From: hauke@hauke-m.de (Hauke Mehrtens)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: BCM5301X: Add LEDs for Netgear R6250 V1
Date: Fri, 03 Oct 2014 16:57:19 +0200 [thread overview]
Message-ID: <542EB94F.7070404@hauke-m.de> (raw)
In-Reply-To: <1412171129-31482-2-git-send-email-zajec5@gmail.com>
On 10/01/2014 03:45 PM, Rafa? Mi?ecki wrote:
> Signed-off-by: Rafa? Mi?ecki <zajec5@gmail.com>
Acked-by: Hauke Mehrtens <hauke@hauke-m.de>
[both patches]
> ---
> arch/arm/boot/dts/bcm4708-netgear-r6250.dts | 34 +++++++++++++++++++++++++++++
> 1 file changed, 34 insertions(+)
>
> diff --git a/arch/arm/boot/dts/bcm4708-netgear-r6250.dts b/arch/arm/boot/dts/bcm4708-netgear-r6250.dts
> index 3b5259d..58d999d 100644
> --- a/arch/arm/boot/dts/bcm4708-netgear-r6250.dts
> +++ b/arch/arm/boot/dts/bcm4708-netgear-r6250.dts
> @@ -32,4 +32,38 @@
> status = "okay";
> };
> };
> +
> + leds {
> + compatible = "gpio-leds";
> +
> + logo {
> + label = "bcm53xx:white:logo";
> + gpios = <&chipcommon 1 GPIO_ACTIVE_HIGH>;
> + linux,default-trigger = "default-on";
> + };
> +
> + power0 {
> + label = "bcm53xx:green:power";
> + gpios = <&chipcommon 2 GPIO_ACTIVE_LOW>;
> + linux,default-trigger = "default-off";
> + };
> +
> + power1 {
> + label = "bcm53xx:amber:power";
> + gpios = <&chipcommon 3 GPIO_ACTIVE_LOW>;
> + linux,default-trigger = "default-on";
> + };
> +
> + usb {
> + label = "bcm53xx:blue:usb";
> + gpios = <&chipcommon 8 GPIO_ACTIVE_LOW>;
> + linux,default-trigger = "default-off";
> + };
> +
> + wireless {
> + label = "bcm53xx:blue:wireless";
> + gpios = <&chipcommon 11 GPIO_ACTIVE_LOW>;
> + linux,default-trigger = "default-off";
> + };
> + };
> };
>
prev parent reply other threads:[~2014-10-03 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 13:45 [PATCH 1/2] ARM: BCM5301X: Add Broadcom's bus-axi to the DTS file Rafał Miłecki
2014-10-01 13:45 ` [PATCH 2/2] ARM: BCM5301X: Add LEDs for Netgear R6250 V1 Rafał Miłecki
2014-10-03 14:57 ` Hauke Mehrtens [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=542EB94F.7070404@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=linux-arm-kernel@lists.infradead.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).