devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: berlin: Add GPIO leds to Google Chromecast
Date: Mon, 20 Oct 2014 16:55:21 +0200	[thread overview]
Message-ID: <54452259.4000402@gmail.com> (raw)
In-Reply-To: <1412351697-4079-1-git-send-email-sebastian.hesselbarth@gmail.com>

On 10/03/2014 05:54 PM, Sebastian Hesselbarth wrote:
> With GPIO support for Marvell Berlin, now add the two gpio-connected
> LEDs on Google Chromecast.
>
> Signed-off-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>

Applied to berlin/dt.

> ---
>   arch/arm/boot/dts/berlin2cd-google-chromecast.dts | 17 +++++++++++++++++
>   1 file changed, 17 insertions(+)
>
> diff --git a/arch/arm/boot/dts/berlin2cd-google-chromecast.dts b/arch/arm/boot/dts/berlin2cd-google-chromecast.dts
> index bcd81ffc495d..0816890a5c0d 100644
> --- a/arch/arm/boot/dts/berlin2cd-google-chromecast.dts
> +++ b/arch/arm/boot/dts/berlin2cd-google-chromecast.dts
> @@ -11,6 +11,7 @@
>   /dts-v1/;
>
>   #include "berlin2cd.dtsi"
> +#include <dt-bindings/gpio/gpio.h>
>
>   / {
>   	model = "Google Chromecast";
> @@ -24,6 +25,22 @@
>   		device_type = "memory";
>   		reg = <0x00000000 0x20000000>; /* 512 MB */
>   	};
> +
> +	leds {
> +		compatible = "gpio-leds";
> +
> +		white {
> +			label = "white";
> +			gpios = <&portc 1 GPIO_ACTIVE_HIGH>;
> +			default-state = "keep";
> +		};
> +
> +		red {
> +			label = "red";
> +			gpios = <&portc 2 GPIO_ACTIVE_HIGH>;
> +			default-state = "keep";
> +		};
> +	};
>   };
>
>   &uart0 { status = "okay"; };
>

      reply	other threads:[~2014-10-20 14:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-03 15:54 [PATCH] ARM: dts: berlin: Add GPIO leds to Google Chromecast Sebastian Hesselbarth
2014-10-20 14:55 ` Sebastian Hesselbarth [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=54452259.4000402@gmail.com \
    --to=sebastian.hesselbarth@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.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).