On Sun, Jun 15, 2014 at 02:23:25AM +0300, Janne Kanniainen wrote: > > Hi! > > Hi. > > >> --- /dev/null > >> +++ b/Documentation/ABI/testing/sysfs-class-hid-driver-gt683r > >> @@ -0,0 +1,10 @@ > >> +What: /sys/class/hidraw/<hidraw>/device/state > >> +Date: Jun 2014 > >> +KernelVersion: 3.15 > >> +Contact: Janne Kanniainen <janne.kanniainen@xxxxxxxxx> > >> +Description: > >> + Set the mode of LEDs > >> + > >> + 0 - normal > >> + 1 - audio > >> + 2 - breathing > > > > THat's some strange interface. Don't we normally use led triggers > > for this? > > I can implement it that way, if you all think that it is correct way. > What do Jiri and Johan thinks of it? > > > And the mode of the LED should really be in /sys/class/leds, not in > > hidraw somewhere... > > The problem is that all panels can only be in one mode at the time. > For example front panel can't be in breathing mode while side panel is > in normal mode. As Janne explained above, it's really an attribute of the parent device and not the individual LEDs. The latter could still use the software timer trigger to blink independently. Johan -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
