**** BEGIN LOGGING AT Wed Dec 14 02:59:57 2022
Dec 14 16:23:02 <sicelo> I will still investigate this properly in the near future (next week?) , but I guess it won't hurt to ask here so long:
Dec 14 16:24:33 <sicelo> lp5523 - I'm playing with the engines and patterns. there's something that's either not explained or I'm missing in wiki and kernel documentation, namely  ... i can make the pattern work and blink as required 
Dec 14 16:26:05 <sicelo> but i don't see how to set color properly, e.g. orange needs r=127 and g=64 brightness. i don't know how to do that. I've read the documentation a couple of  times, and couldn't find it
Dec 14 16:28:52 <sicelo> tldr; how can i produce the *orange* battery charging pattern using the led engines facilities 
Dec 14 22:17:06 <sicelo> solved. the trick is in `led_current`. mainline has higher values, so the LED is much brighter, and shows different color as a result.
Dec 14 22:24:06 <L29Ah> sicelo: do you mean it's commanding 100% to red but it turns out orange due to excessive current?
Dec 14 22:26:21 <sicelo> i found the problem with, `echo 100 | tee red/brightness | tee green/brightness`. on the two devices, the same command gave different colors. on the mainline device, it looked more green than orange, while on the maemo device it's orange
Dec 14 22:27:10 <sicelo> i'm not sure what sets the current in maemo, but at least i now know the led engines work fine
Dec 14 22:30:37 <sicelo> with mainline, both leds (green and red) had 50mA. i guess the green overpowers the red. in maemo, green had 2, and red had 20. setting the same on mainline produces the expected color
Dec 14 22:42:47 <sicelo> actually, rtfm ... the wiki states this somewhat, but i guess in my rush, i didn't take note of the section that says:
Dec 14 22:42:53 <sicelo> "So the driver init default "50" for all LEDs is 5 mA, and mce seems to set current to 0.2 mA (value 2 in the led_current sysnode) for B and G, and either to 0.2 mA or 0.8 mA for R."
**** ENDING LOGGING AT Thu Dec 15 02:59:56 2022