| joerg | sicelo: >>when you disable an engine, and if an led was turned on at that moment, it remains on<< that seems highly plausible to me. In the end the engines only write values to the hardware registers for PWM alias LEd brightness | 07:50 |
|---|---|---|
| joerg | sicelo: where do I find that "kernel model" you mentioned? | 08:02 |
| sicelo | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/leds/leds-lp5523.c | 08:04 |
| sicelo | maybe i was wrong - it might not be too different from the original driver :-) | 08:05 |
| * joerg just wonders how buggy the implementation of /sys/class/i2c-adapter/i2c-2/2-0032/leds:lp5523:*/trigger behavior. When used ( echo heartbeat >trigger ) it seems to kill the normal engine behavior, maybe even for *all* 9 LEDs driven by that lp5523 chip | 08:07 | |
| joerg | hmmmm | 08:49 |
| sicelo | what do you have in mind | 09:08 |
| joerg | sicelo: I tried to understand how fubar that kernel module leds-lp5523.ko actually is | 16:12 |
| joerg | I'm probably just too long out of coding business to understand what made them consider it a good idea to implement https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/leds/leds-lp5523.c#n271 instead of simply writing map data to register addr 0x70 ENG1 MAPPING MSB ~ 0x75 ENG3 MAPPING LSB | 16:16 |
| joerg | same context/fubarf: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/leds/leds-lp5523.c#n24 ~ n31 | 16:17 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!