On Mon, Sep 15, 2014 at 04:41:42PM -0700, Michael Wright wrote: > > LEDs should be controlled via LED subsystem. The fact that they happen > > to be located on a given device does not mean they belong to input > > subsystem. The same as LEds on network card are not part of network stack, > > etc. > > I think the fundamental difference for me is that the primary input > standard does > have a specification for how to interact with LEDs, ... That predates LED subsystem. When we saw that it is not flexible enough LED subsystem was created. Input, for better or worse, has "sound" support as well, but I do not think anyone would want to to enhance it to support 7.1 surround output ;) > and right now the LED > subsystem has no knowledge of HID whatsoever. Then that is something that needs to be changed. > > Even if I did add the plumbing for HID over into the LED subsystem, is there an > easy way to correlate input devices and their LEDs from userspace? What does it mean "their led"? The led that happens to share the same physical package? Thanks. -- Dmitry -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
