devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Vladimir Barinov <vladimir.barinov@cogentembedded.com>
Cc: Magnus Damm <magnus.damm@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v5 1/4] arm64: dts: h3ulcb: enable GPIO leds
Date: Mon, 5 Sep 2016 14:26:56 +0200	[thread overview]
Message-ID: <20160905122656.GH24256@verge.net.au> (raw)
In-Reply-To: <1472833488-26184-1-git-send-email-vladimir.barinov@cogentembedded.com>

On Fri, Sep 02, 2016 at 07:24:48PM +0300, Vladimir Barinov wrote:
> This supports GPIO leds on H3ULCB board
> 
> Signed-off-by: Vladimir Barinov <vladimir.barinov@cogentembedded.com>
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> Changes in version 3:
> - initially added
> Changes in version 4:
> - removed led4 in favor of gpio-keys
> - added label
> Changes in version 5:
> - nothing
> 
>  arch/arm64/boot/dts/renesas/r8a7795-h3ulcb.dts | 13 +++++++++++++
>  1 file changed, 13 insertions(+)
> 
> diff --git a/arch/arm64/boot/dts/renesas/r8a7795-h3ulcb.dts b/arch/arm64/boot/dts/renesas/r8a7795-h3ulcb.dts
> index fb694b8..3329f78 100644
> --- a/arch/arm64/boot/dts/renesas/r8a7795-h3ulcb.dts
> +++ b/arch/arm64/boot/dts/renesas/r8a7795-h3ulcb.dts
> @@ -31,6 +31,19 @@
>  		/* first 128MB is reserved for secure area. */
>  		reg = <0x0 0x48000000 0x0 0x38000000>;
>  	};
> +
> +	leds {
> +		compatible = "gpio-leds";
> +
> +		led5 {
> +			label = "LED5";
> +			gpios = <&gpio6 12 GPIO_ACTIVE_HIGH>;
> +		};
> +		led6 {
> +			label = "LED6";
> +			gpios = <&gpio6 13 GPIO_ACTIVE_HIGH>;
> +		};
> +	};
>  };

Please remove the label properties.

  reply	other threads:[~2016-09-05 12:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-02 16:23 [PATCH v5 0/4] arm64: renesas: enable H3ULCB board peripherals Vladimir Barinov
     [not found] ` <1472833419-26139-1-git-send-email-vladimir.barinov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2016-09-02 16:24   ` [PATCH v5 1/4] arm64: dts: h3ulcb: enable GPIO leds Vladimir Barinov
2016-09-05 12:26     ` Simon Horman [this message]
2016-09-02 16:24   ` [PATCH v5 2/4] arm64: dts: h3ulcb: enable GPIO keys Vladimir Barinov
2016-09-05  7:57     ` Geert Uytterhoeven
     [not found]       ` <CAMuHMdWXq8enfSUcwFK=6NXoZgJkqo=iScjO8A3ZO-sGrcxb4w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-09-05 12:17         ` Simon Horman
2016-09-02 16:25   ` [PATCH v5 3/4] arm64: dts: h3ulcb: enable SDHI0 Vladimir Barinov
     [not found]     ` <1472833508-26267-1-git-send-email-vladimir.barinov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2016-09-05 12:25       ` Simon Horman
2016-09-02 16:25   ` [PATCH v5 4/4] arm64: dts: h3ulcb: Sound SSI support Vladimir Barinov
     [not found]     ` <1472833529-26308-1-git-send-email-vladimir.barinov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2016-09-05  0:27       ` Kuninori Morimoto
     [not found]         ` <8737lf42rx.wl%kuninori.morimoto.gx-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org>
2016-09-05 12:26           ` Simon Horman

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=20160905122656.GH24256@verge.net.au \
    --to=horms@verge.net.au \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=vladimir.barinov@cogentembedded.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).