From: Tony Lindgren <tony@atomide.com>
To: Sebastian Reichel <sre@kernel.org>
Cc: Richard Purdie <rpurdie@rpsys.net>,
Jacek Anaszewski <jacek.anaszewski@gmail.com>,
Pavel Machek <pavel@ucw.cz>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] ARM: dts: motorola-cpcap-mapphone: add LEDs
Date: Mon, 6 Mar 2017 08:11:18 -0800 [thread overview]
Message-ID: <20170306161118.GI20572@atomide.com> (raw)
In-Reply-To: <20170305172234.24120-2-sre@kernel.org>
* Sebastian Reichel <sre@kernel.org> [170305 09:24]:
> Signed-off-by: Sebastian Reichel <sre@kernel.org>
> ---
> arch/arm/boot/dts/motorola-cpcap-mapphone.dtsi | 30 ++++++++++++++++++++++++++
> 1 file changed, 30 insertions(+)
>
> diff --git a/arch/arm/boot/dts/motorola-cpcap-mapphone.dtsi b/arch/arm/boot/dts/motorola-cpcap-mapphone.dtsi
> index 9970985e685b..e02982d69854 100644
> --- a/arch/arm/boot/dts/motorola-cpcap-mapphone.dtsi
> +++ b/arch/arm/boot/dts/motorola-cpcap-mapphone.dtsi
> @@ -38,6 +38,36 @@
>
> interrupts = <23 IRQ_TYPE_NONE>;
> };
> +
> + led_red: led-red {
> + compatible = "motorola,cpcap-led-red";
> + vdd-supply = <&sw5>;
> + label = "status-led:red";
> + };
> +
> + led_green: led-green {
> + compatible = "motorola,cpcap-led-green";
> + vdd-supply = <&sw5>;
> + label = "status-led:green";
> + };
> +
> + led_blue: led-blue {
> + compatible = "motorola,cpcap-led-blue";
> + vdd-supply = <&sw5>;
> + label = "status-led:blue";
> + };
> +
> + led_adl: led-adl {
> + compatible = "motorola,cpcap-led-adl";
> + vdd-supply = <&sw5>;
> + label = "button-backlight";
> + };
> +
> + led_cp: led-cp {
> + compatible = "motorola,cpcap-led-cp";
> + vdd-supply = <&sw5>;
> + label = "shift-key-light";
> + };
> };
> };
Applying into omap-for-v4.12/dt-droid4 thanks. I added minimal
description to the patch saying "Add LEDs".
Regards,
Tony
next prev parent reply other threads:[~2017-03-06 16:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-05 17:22 [PATCH 1/2] leds: cpcap: new driver Sebastian Reichel
2017-03-05 17:22 ` [PATCH 2/2] ARM: dts: motorola-cpcap-mapphone: add LEDs Sebastian Reichel
2017-03-06 16:11 ` Tony Lindgren [this message]
2017-03-06 21:41 ` [PATCH 1/2] leds: cpcap: new driver Jacek Anaszewski
2017-03-06 22:11 ` Pavel Machek
2017-03-06 23:38 ` Tony Lindgren
2017-03-07 11:55 ` Pavel Machek
2017-03-07 16:26 ` Tony Lindgren
2017-04-11 20:20 ` Pavel Machek
2017-03-07 17:19 ` Sebastian Reichel
2017-04-11 20:19 ` Pavel Machek
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=20170306161118.GI20572@atomide.com \
--to=tony@atomide.com \
--cc=devicetree@vger.kernel.org \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--cc=rpurdie@rpsys.net \
--cc=sre@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).