Hi! > > > It is *function* and maybe color that userspace is interested in, and > > > here we have proper standardization in form of "kbd_backlight". Device > > > name is, well, device name. It should uniquely identify the device led > > > is attached to, but otherwise is rarely interesting. If userspace is > > > really concerned what kind of keyboard backlight it is it should > > > investigate parent device(s) and see what they end up with. > > > > That does not work. Userspace wants to know if it is internal keyboard > > or USB keyboard, not what kind of i2c controller the LED is connected > > to. > > Why does userspace want to know it? For example to turn off backlight on internal keyboard when the lid is closed. > > grep for platform::mic_mute . > > > > (And platform is even pretty good match for how the LED is connected > > in your case). > > Until we get a secondary interface that is also "platform"... How would that happen? Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Attachment:
signature.asc
Description: Digital signature
