**** BEGIN LOGGING AT Fri Dec 16 02:59:56 2022
Dec 16 06:50:36 <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
Dec 16 07:02:45 <joerg> sicelo: where do I find that "kernel model" you mentioned?
Dec 16 07:04:26 <sicelo> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/leds/leds-lp5523.c
Dec 16 07:05:13 <sicelo> maybe i was wrong - it might not be too different from the original driver :-)
Dec 16 07:07:11 * 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
Dec 16 07:49:13 <joerg> hmmmm  
Dec 16 08:08:45 <sicelo> what do you have in mind
Dec 16 15:12:47 <joerg> sicelo: I tried to understand how fubar that kernel module leds-lp5523.ko actually is
Dec 16 15:16:05 <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
Dec 16 15:17:48 <joerg> same context/fubarf: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/leds/leds-lp5523.c#n24 ~ n31
**** ENDING LOGGING AT Sat Dec 17 02:59:56 2022