From: Pavel Machek <pavel@ucw.cz>
To: Merlijn Wajer <merlijn@wizzup.org>
Cc: "Ivaylo Dimitrov" <ivo.g.dimitrov.75@gmail.com>,
"Dev Null" <devnull@uvos.xyz>, "Tony Lindgren" <tony@atomide.com>,
"Sebastian Reichel" <sre@kernel.org>,
linux-omap@vger.kernel.org, "Arnd Bergmann" <arnd@arndb.de>,
"Olof Johansson" <olof@lixom.net>,
soc@kernel.org, "Rob Herring" <robh+dt@kernel.org>,
"Benoît Cousson" <bcousson@baylibre.com>,
"Kees Cook" <keescook@chromium.org>,
"Anton Vorontsov" <anton@enomsg.org>,
"Colin Cross" <ccross@android.com>,
"Tony Luck" <tony.luck@intel.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 2/2] Droid3: add initial DTS
Date: Sun, 19 Dec 2021 14:17:34 +0100 [thread overview]
Message-ID: <20211219131734.GA28481@duo.ucw.cz> (raw)
In-Reply-To: <20211212230459.13579-3-merlijn@wizzup.org>
[-- Attachment #1: Type: text/plain, Size: 396 bytes --]
Hi!
> + backlight_led: led@0 {
...
> + label = ":backlight";
> + };
This is same as Droid 4, good.
> + led@1 {
...
> + label = ":kbd_backlight";
> + };
> + };
This one is new. We should make sure it is same label as on PCs, and
then document it in Documentation/leds/well-known-leds.txt .
Best regards,
Pavel
--
http://www.livejournal.com/~pavelmachek
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2021-12-19 13:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211212230459.13579-1-merlijn@wizzup.org>
2021-12-12 23:04 ` [RFC PATCH 1/2] pmic-cpcap: add motorola,droid3 compatible Merlijn Wajer
2021-12-13 5:57 ` Tony Lindgren
2021-12-13 10:37 ` Merlijn Wajer
2021-12-15 8:42 ` Tony Lindgren
2021-12-12 23:04 ` [RFC PATCH 2/2] Droid3: add initial DTS Merlijn Wajer
2021-12-13 6:01 ` Tony Lindgren
2021-12-14 21:30 ` Merlijn Wajer
2021-12-19 13:17 ` Pavel Machek [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=20211219131734.GA28481@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=anton@enomsg.org \
--cc=arnd@arndb.de \
--cc=bcousson@baylibre.com \
--cc=ccross@android.com \
--cc=devicetree@vger.kernel.org \
--cc=devnull@uvos.xyz \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=merlijn@wizzup.org \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=soc@kernel.org \
--cc=sre@kernel.org \
--cc=tony.luck@intel.com \
--cc=tony@atomide.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).