From: Pavel Machek <pavel@ucw.cz>
To: Jacek Anaszewski <jacek.anaszewski@gmail.com>
Cc: linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
robh@kernel.org, sakari.ailus@iki.fi, dmurphy@ti.com
Subject: Re: [PATCH/RFC] DT: leds: Fix 'label' property description and add 'colour' property
Date: Mon, 4 Dec 2017 11:43:51 +0100 [thread overview]
Message-ID: <20171204104351.GA6611@amd> (raw)
In-Reply-To: <1512251410-6084-1-git-send-email-jacek.anaszewski@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2204 bytes --]
Hi!
> Label property was imposed a uniqueness requirement, which was erroneous,
> since ePAPR defines it to "a human readable string describing a device".
>
> Also the binding description misleadingly suggested direct usage of label
> for LED class device name, whereas it should only define a LED function.
>
> Therefore an additional 'colour' property is being introduced, which together
> with the parent DT node name used for devicename shall be used for naming LED
> class device according to the patterh
> <devicename>:<colour>:<function>.
> -- label : The label for this LED. If omitted, the label is taken from the node
> - name (excluding the unit address). It has to uniquely identify
> - a device, i.e. no other LED class device can be assigned the same
> - label.
> +- label : The label for this LED. It should describe its function. If omitted,
> + the label is taken from the node name (excluding the unit address).
So the label contains "as1235:green:capslock"? I guess it might be
nice to mention that. Or just the "capslock" part?
Also.. it would be good to start pushing for more consistency in the
labels: I have these on the thinkpad:
input5::scrolllock/ tpacpi::dock_status2/ tpacpi::unknown_led/
mmc0::/ tpacpi:green:batt/ tpacpi::unknown_led2/
phy0-led/ tpacpi:orange:batt/ tpacpi::unknown_led3/
tpacpi::bay_active/ tpacpi::power/
On embedded system, I'd like to see <devicename> to corespond
to.. device the led belongs to, as opposed to name of the chip that
drives the led. Maybe we should do 'main_camera:white:flash' instead of
'as4132:white:flash' because userspace already has information on what
chip it is (sysfs paths), but can not easily figure out to which
device the flash belongs.
> +- colour : Colour of the LED.
>
> - default-state : The initial state of the LED. Valid values are "on", "off",
> and "keep". If the LED is already on or off and the default-state
> - property is
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-12-04 10:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-02 21:50 [PATCH/RFC] DT: leds: Fix 'label' property description and add 'colour' property Jacek Anaszewski
2017-12-04 10:43 ` Pavel Machek [this message]
2017-12-05 19:52 ` Jacek Anaszewski
2017-12-11 16:27 ` Rob Herring
2017-12-14 21:35 ` Jacek Anaszewski
[not found] ` <82dc0ed3-f4fe-d8a2-65ea-4212770b78e7-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-12-17 12:49 ` Jacek Anaszewski
2018-03-02 12:51 ` Pavel Machek
2017-12-08 16:01 ` Dan Murphy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171204104351.GA6611@amd \
--to=pavel@ucw.cz \
--cc=dmurphy@ti.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sakari.ailus@iki.fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).