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 4/9] arm64: dts: m3ulcb: enable GPIO leds
Date: Mon, 7 Nov 2016 13:57:37 +0100 [thread overview]
Message-ID: <20161107125737.GF12319@verge.net.au> (raw)
In-Reply-To: <1478196451-1298-1-git-send-email-vladimir.barinov@cogentembedded.com>
On Thu, Nov 03, 2016 at 09:07:31PM +0300, Vladimir Barinov wrote:
> This supports GPIO leds on M3ULCB board
Are GPIO leds and keys also present on the H3ULCB.
If so could you consider sending patches to enable them?
> Signed-off-by: Vladimir Barinov <vladimir.barinov@cogentembedded.com>
> ---
> arch/arm64/boot/dts/renesas/r8a7796-m3ulcb.dts | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/renesas/r8a7796-m3ulcb.dts b/arch/arm64/boot/dts/renesas/r8a7796-m3ulcb.dts
> index fb694b8..3329f78 100644
> --- a/arch/arm64/boot/dts/renesas/r8a7796-m3ulcb.dts
> +++ b/arch/arm64/boot/dts/renesas/r8a7796-m3ulcb.dts
> @@ -31,6 +31,17 @@
> /* first 128MB is reserved for secure area. */
> reg = <0x0 0x48000000 0x0 0x38000000>;
> };
> +
> + leds {
> + compatible = "gpio-leds";
> +
> + led5 {
> + gpios = <&gpio6 12 GPIO_ACTIVE_HIGH>;
> + };
> + led6 {
> + gpios = <&gpio6 13 GPIO_ACTIVE_HIGH>;
> + };
> + };
> };
>
> &extal_clk {
> --
> 1.9.1
>
WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
To: Vladimir Barinov
<vladimir.barinov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
Cc: Magnus Damm <magnus.damm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-renesas-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 4/9] arm64: dts: m3ulcb: enable GPIO leds
Date: Mon, 7 Nov 2016 13:57:37 +0100 [thread overview]
Message-ID: <20161107125737.GF12319@verge.net.au> (raw)
In-Reply-To: <1478196451-1298-1-git-send-email-vladimir.barinov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
On Thu, Nov 03, 2016 at 09:07:31PM +0300, Vladimir Barinov wrote:
> This supports GPIO leds on M3ULCB board
Are GPIO leds and keys also present on the H3ULCB.
If so could you consider sending patches to enable them?
> Signed-off-by: Vladimir Barinov <vladimir.barinov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
> ---
> arch/arm64/boot/dts/renesas/r8a7796-m3ulcb.dts | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/renesas/r8a7796-m3ulcb.dts b/arch/arm64/boot/dts/renesas/r8a7796-m3ulcb.dts
> index fb694b8..3329f78 100644
> --- a/arch/arm64/boot/dts/renesas/r8a7796-m3ulcb.dts
> +++ b/arch/arm64/boot/dts/renesas/r8a7796-m3ulcb.dts
> @@ -31,6 +31,17 @@
> /* first 128MB is reserved for secure area. */
> reg = <0x0 0x48000000 0x0 0x38000000>;
> };
> +
> + leds {
> + compatible = "gpio-leds";
> +
> + led5 {
> + gpios = <&gpio6 12 GPIO_ACTIVE_HIGH>;
> + };
> + led6 {
> + gpios = <&gpio6 13 GPIO_ACTIVE_HIGH>;
> + };
> + };
> };
>
> &extal_clk {
> --
> 1.9.1
>
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-11-07 12:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 18:06 [PATCH 0/9] arm64: renesas: add M3ULCB board Vladimir Barinov
2016-11-03 18:06 ` [PATCH 1/9] dt: arm: shmobile: add M3ULCB board DT bindings Vladimir Barinov
2016-11-03 18:07 ` [PATCH 2/9] arm64: dts: m3ulcb: initial device tree Vladimir Barinov
2016-11-03 18:07 ` [PATCH 3/9] arm64: dts: m3ulcb: enable SCIF clk and pins Vladimir Barinov
2016-11-03 18:07 ` [PATCH 4/9] arm64: dts: m3ulcb: enable GPIO leds Vladimir Barinov
2016-11-07 12:57 ` Simon Horman [this message]
2016-11-07 12:57 ` Simon Horman
2016-11-07 13:02 ` Vladimir Barinov
2016-11-03 18:07 ` [PATCH 5/9] arm64: dts: m3ulcb: enable GPIO keys Vladimir Barinov
2016-11-03 18:07 ` Vladimir Barinov
2016-11-03 18:07 ` [PATCH 6/9] arm64: dts: m3ulcb: enable SDHI0 Vladimir Barinov
2016-11-07 13:00 ` Simon Horman
2016-11-07 13:05 ` Vladimir Barinov
2016-11-07 13:05 ` Vladimir Barinov
2016-11-03 18:08 ` [PATCH 7/9] arm64: dts: m3ulcb: enable EXTALR clk Vladimir Barinov
2016-11-03 18:08 ` Vladimir Barinov
2016-11-03 18:08 ` [PATCH 8/9] arm64: dts: m3ulcb: enable WDT Vladimir Barinov
2016-11-03 18:08 ` [PATCH 9/9] arm64: dts: m3ulcb: enable SDHI2 Vladimir Barinov
2016-11-07 13:35 ` [PATCH 0/9] arm64: renesas: add M3ULCB board Simon Horman
2016-11-07 13:35 ` Simon Horman
2016-11-08 14:14 ` [PATCH 6/9 v2] arm64: dts: m3ulcb: enable SDHI0 Vladimir Barinov
2016-11-09 7:44 ` Simon Horman
2016-11-09 7:44 ` Simon Horman
2016-11-09 8:06 ` Vladimir Barinov
2016-11-08 14:14 ` [PATCH 9/9 v2] arm64: dts: m3ulcb: enable SDHI2 Vladimir Barinov
2016-11-08 14:14 ` Vladimir Barinov
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=20161107125737.GF12319@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.