[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdYJNWC3RZXjCu+3EfRbPy6OyLLw-FivpFoe1p3ckHTCmg@mail.gmail.com>
Date: Mon, 12 Nov 2018 22:23:13 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Pavel Machek <pavel@....cz>
Cc: Jacek Anaszewski <jacek.anaszewski@...il.com>,
linux-leds@...r.kernel.org,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Rob Herring <robh@...nel.org>,
Baolin Wang <baolin.wang@...aro.org>,
Daniel Mack <daniel@...que.org>, dmurphy@...com,
oleg@....org.ua, Sakari Ailus <sakari.ailus@...ux.intel.com>,
simon@...eageos.org, xiaotong.lu@...eadtrum.com
Subject: Re: [PATCH 02/24] leds: core: Add support for composing LED class
device names
On Sun, Nov 11, 2018 at 1:03 PM Pavel Machek <pavel@....cz> wrote:
> > -"devicename:colour:function"
> > +"colour:function"
>
> I don't think we want to do it in all cases.
>
> So, on my cellphone seeing lp5523:green:led is indeed not useful.
>
> But on notebook with usb keyboard attached, you need to keep the
> devicename to be able to distinguish capslock on internal keyboard and
> capslock on first USB keyboard and capslock on second USB keyboard.
I agree with Pavel.
I ran into this when connecting two identical keyboards to the
same machine. The driver worked fine up until it tries
to create two sysfs entries with the same name for capslock.
BOOM!
In this case I suggest "serialnumber:color:capslock" and
similar.
The important point is the string must be unique for each
plugged device.
Yours,
Linus Walleij
Powered by blists - more mailing lists