| ↑back Search ←Prev date Next date→ Show only urls | (Click on time to select a line by its url) |
| Who | What | When |
|---|---|---|
| *** | benjiG has left | [15:55] |
| .................................................. (idle for 4h7mn) | ||
| z3ntu | Hey, can somebody explain me how "timeout" stuff in led_classdev_flash is supposed to work or how it's used?
I'm working on a driver for a relatively dumb flash light which is controlled via two gpio pins (one for enable, one for toggling between flash mode and torch mode - flash mode works for about 200-300ms and then switches to torch mode, so it should be turned off again by the driver I guess?) Unfortunately documentation for flash devices is pretty sparse :( | [20:02] |
| ........ (idle for 35mn) | ||
| sailus | z3ntu: The driver should turn it off, yes.
You could also check the V4L2 flash control documentation: https://hverkuil.home.xs4all.nl/spec/uapi/v4l/ext-ctrls-flash.html | [20:43] |
| ................... (idle for 1h34mn) | ||
| z3ntu | sailus: Could you give me some hints what I have to do driver-side to get it working as it's supposed to? Source is at https://gitlab.com/pine64-org/linux/blob/pine64-kernel-5.4.y-flash/drivers/leds/leds-sgm3140.c . I understand that my flash device is a "Unsynchronised LED flash (software strobe)" and "LED flash as torch" but I'm quite unsure on how this should get implemented. | [22:18] |
| ↑back Search ←Prev date Next date→ Show only urls | (Click on time to select a line by its url) |