From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: Mohammad Rasim <mohammad.rasim96@gmail.com>
Cc: devicetree@vger.kernel.org, linux-amlogic@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
Kevin Hilman <khilman@baylibre.com>,
Neil Armstrong <narmstrong@baylibre.com>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v3 2/2] arm64: dts: meson-gxbb: add support for
Date: Sat, 30 Nov 2019 20:25:26 +0100 [thread overview]
Message-ID: <CAFBinCD4otHpey+A3G2sdo1K-Z8Ed6OSa2BerW-q7t9irZPnvg@mail.gmail.com> (raw)
In-Reply-To: <20191130190702.52zjhlh65gpq2ugj@manjaro.localdomain>
On Sat, Nov 30, 2019 at 8:07 PM Mohammad Rasim
<mohammad.rasim96@gmail.com> wrote:
[...]
> > > > > + leds {
> > > > > + compatible = "gpio-leds";
> > > > > + red {
> > > > > + label = "status";
> > > > this property seems to be deprecated now, see
> > > > Documentation/devicetree/bindings/leds/common.txt
> > > > but I'm not sure whether Kevin has made a decision yet when to not
> > > > accept "label" properties here anymore
> > > OK, I will remove the deprecated property
> > > but I'm not sure what should I choose as a function, LED_FUNCTION_STATUS
> > > or LED_FUNCTION_ACTIVITY ?
> > I haven't used function and color myself but I believe it works like
> > this (untested):
> > - add an #include <dt-bindings/leds/common.h> next to the other
> > #includes (keep alphabetical ordering). this include file also
> > contains all the #defines for color and function
> > - add a color property, for example: color = <LED_COLOR_ID_RED>;
> > - add a function property, for example: function = <LED_FUNCTION_STATUS>;
> > - test, debug and fix potential issues ;)
> Yes, I've already tested it but I'm just not sure what should be in the
> function property, LED_FUNCTION_STATUS and LED_FUNCTION_ACTIVITY both
> seem like good choices,
I haven't considered "activity" before, but most of our boards with
some kind of status LED use status in the label
unless someone objects: choose the one you like most
[...]
> if this property only used to lable the led then LED_FUNCTION_STATUS is
> ok, but maybe this is used by userspace to trigger the led ?!
in general devicetree describes hardware
I don't know if userspace does something "automatically" based on the
function. however, my expectation is that the trigger from
"linux,default-trigger" is used (if set) and that you can change the
trigger from userspace manually (if you wish)
Martin
prev parent reply other threads:[~2019-11-30 19:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191130115824.31778-1-mohammad.rasim96@gmail.com>
2019-11-30 11:58 ` [PATCH v3 1/2] dt-bindings: Add vendor prefix for Videostrong Mohammad Rasim
2019-11-30 13:45 ` Martin Blumenstingl
2019-11-30 17:11 ` Mohammad Rasim
2019-11-30 11:58 ` [PATCH v3 2/2] arm64: dts: meson-gxbb: add support for Mohammad Rasim
2019-11-30 13:59 ` Martin Blumenstingl
2019-11-30 17:47 ` Mohammad Rasim
2019-11-30 18:57 ` Martin Blumenstingl
2019-11-30 19:07 ` Mohammad Rasim
2019-11-30 19:12 ` Mohammad Rasim
2019-11-30 19:25 ` Martin Blumenstingl [this message]
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=CAFBinCD4otHpey+A3G2sdo1K-Z8Ed6OSa2BerW-q7t9irZPnvg@mail.gmail.com \
--to=martin.blumenstingl@googlemail.com \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mohammad.rasim96@gmail.com \
--cc=narmstrong@baylibre.com \
--cc=robh+dt@kernel.org \
/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).