linux-kernel - Re: [PATCH v5] leds: USB: HID: Add support for MSI GT683R led panels

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140616074503.GB20636@localhost>
Date:	Mon, 16 Jun 2014 09:45:03 +0200
From:	Johan Hovold <johan@...nel.org>
To:	Janne Kanniainen <janne.kanniainen@...il.com>
Cc:	Pavel Machek <pavel@....cz>, Jiri Kosina <jkosina@...e.cz>,
	Johan Hovold <johan@...nel.org>, Bryan Wu <cooloney@...il.com>,
	linux-kernel@...r.kernel.org, linux-leds@...r.kernel.org,
	linux-usb@...r.kernel.org, linux-input@...r.kernel.org
Subject: Re: [PATCH v5] leds: USB: HID: Add support for MSI GT683R led panels

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@...il.com>
> >> +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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/