Message ID | 20230328161541.599463-1-jjhiblot@traphandler.com |
---|---|
Headers | show |
Series | Add a multicolor LED driver for groups of monochromatic LEDs | expand |
On Tue, Mar 28, 2023 at 7:15 PM Jean-Jacques Hiblot <jjhiblot@traphandler.com> wrote: > > This information might be useful for more than only deriving the led's > name. And since we have this information, we can expose it in the sysfs. ... > +Date: March 2023 > +KernelVersion: 6.3 Outdated version. ... > + Color of the led. > + > + This is a read-only file. Reading this file returns the color > + of the led as a string (ex: "red", "green"). There are no strict rules about colour and I don't think it's a good idea. Why in such a case is it different to label? My proposal here at least documenting that the colour must follow one of the existing naming standards (like RGB in hex, HTML, or name in accordance with chosen standard). Yet, it won't technically prevent abusing that, but at least will show the intention and allow pointing out to the bugs or develop user space tooling based on existing parsers (if any).
On 28/03/2023 19:15, Andy Shevchenko wrote: > On Tue, Mar 28, 2023 at 7:15 PM Jean-Jacques Hiblot > <jjhiblot@traphandler.com> wrote: >> >> This information might be useful for more than only deriving the led's >> name. And since we have this information, we can expose it in the sysfs. > > ... > >> +Date: March 2023 >> +KernelVersion: 6.3 > > Outdated version. > > ... > >> + Color of the led. >> + >> + This is a read-only file. Reading this file returns the color >> + of the led as a string (ex: "red", "green"). > > There are no strict rules about colour and I don't think it's a good > idea. Why in such a case is it different to label? My proposal here at > least documenting that the colour must follow one of the existing > naming standards (like RGB in hex, HTML, or name in accordance with > chosen standard). Actually the colors are defined in an array: led_colors (led-core.c: 88) So the color is one of the following: white, red, reen, blue, amber, violet, yellow, ir, multicolor, rgb There is mention in the TODO file of changing the way RGB leds are handled and the RGB leds would probably show the hex RGB values here. > > Yet, it won't technically prevent abusing that, but at least will show > the intention and allow pointing out to the bugs or develop user space > tooling based on existing parsers (if any). >
On 28/03/2023 18:15, Jean-Jacques Hiblot wrote: > Some HW design implement multicolor LEDs with several monochromatic LEDs. > Grouping the monochromatic LEDs allows to configure them in sync and use > the triggers. > The PWM multicolor LED driver implements such grouping but only for > PWM-based LEDs. As this feature is also desirable for the other types of > LEDs, this series implements it for any kind of LED device. > > changes v7->v8: > - consistently use "LEDs group multicolor" throughout the code. > - rename some variables with more explicit names. > - improve comments. > - use the 100-characters per line limit. > Hi Lee, Are there any pending items regarding this series ? If not, can you consider merging it ? Thanks, JJ
On Fri 2023-04-28 14:39:20, Jean-Jacques Hiblot wrote: > On 28/03/2023 18:15, Jean-Jacques Hiblot wrote: > > Some HW design implement multicolor LEDs with several monochromatic LEDs. > > Grouping the monochromatic LEDs allows to configure them in sync and use > > the triggers. > > The PWM multicolor LED driver implements such grouping but only for > > PWM-based LEDs. As this feature is also desirable for the other types of > > LEDs, this series implements it for any kind of LED device. > > > > changes v7->v8: > > - consistently use "LEDs group multicolor" throughout the code. > > - rename some variables with more explicit names. > > - improve comments. > > - use the 100-characters per line limit. > > > Hi Lee, > > Are there any pending items regarding this series ? > If not, can you consider merging it ? We should not be merging it in the middle of merge window... right? BR, Pavel