From: Pavel Machek <pavel@ucw.cz>
To: Rob Herring <robh@kernel.org>
Cc: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
jacek.anaszewski@gmail.com, dmurphy@ti.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-leds@vger.kernel.org, thunder.leizhen@huawei.com
Subject: Re: [PATCH v2] dt-bindings: leds: Document commonly used LED triggers
Date: Wed, 30 Dec 2020 20:20:57 +0100 [thread overview]
Message-ID: <20201230192057.GF25903@duo.ucw.cz> (raw)
In-Reply-To: <20201214223621.GA2493849@robh.at.kernel.org>
[-- Attachment #1: Type: text/plain, Size: 782 bytes --]
On Mon 2020-12-14 16:36:21, Rob Herring wrote:
> On Thu, Dec 10, 2020 at 01:54:49PM +0530, Manivannan Sadhasivam wrote:
> > This commit documents the LED triggers used commonly in the SoCs. Not
> > all triggers are documented as some of them are very application specific.
> > Most of the triggers documented here are currently used in devicetrees
> > of many SoCs.
>
> The idea with recent LED binding changes is to move away from
> 'linux,default-trigger' to 'function' and 'trigger-sources' and to have
> some sort of standardized names.
Yes, but I guess we still want to document this... and perhaps use it
during transition and when trigger-sources (etc) are too hard to set
up.
Best regards,
Pavel
--
http://www.livejournal.com/~pavelmachek
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2020-12-30 19:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 8:24 [PATCH v2] dt-bindings: leds: Document commonly used LED triggers Manivannan Sadhasivam
2020-12-13 2:39 ` Leizhen (ThunderTown)
2020-12-13 3:03 ` Leizhen (ThunderTown)
2020-12-14 22:36 ` Rob Herring
2020-12-30 19:20 ` Pavel Machek [this message]
2021-01-27 1:38 ` Leizhen (ThunderTown)
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=20201230192057.GF25903@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=robh@kernel.org \
--cc=thunder.leizhen@huawei.com \
/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).