From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: rk3188-radxarock: add GPIO IR receiver node
Date: Sun, 13 Jul 2014 14:37:40 +0200 [thread overview]
Message-ID: <2390327.HZxnbJmfOO@diego> (raw)
In-Reply-To: <1405253401-15534-1-git-send-email-b.galvani@gmail.com>
Am Sonntag, 13. Juli 2014, 14:10:01 schrieb Beniamino Galvani:
> This adds a device tree node for the infrared receiver connected to a
> GPIO pin on the Radxa Rock.
>
> Signed-off-by: Beniamino Galvani <b.galvani@gmail.com>
> ---
> arch/arm/boot/dts/rk3188-radxarock.dts | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/arch/arm/boot/dts/rk3188-radxarock.dts
> b/arch/arm/boot/dts/rk3188-radxarock.dts index 19d45b4..1d87bcb 100644
> --- a/arch/arm/boot/dts/rk3188-radxarock.dts
> +++ b/arch/arm/boot/dts/rk3188-radxarock.dts
> @@ -23,6 +23,13 @@
> reg = <0x60000000 0x80000000>;
> };
>
> + ir_recv: ir-receiver {
> + compatible = "gpio-ir-receiver";
> + gpios = <&gpio0 10 1>;
> + pinctrl-names = "default";
> + pinctrl-0 = <&ir_recv_pin>;
> + };
> +
hmm, on second glance, I'm actually not sure if this shouldn't belong in the
soc subnode, like the gpio-keys and leds.
Heiko
> soc {
> uart0: serial at 10124000 {
> status = "okay";
> @@ -117,6 +124,12 @@
> rockchip,pins = <RK_GPIO3 27 RK_FUNC_GPIO
&pcfg_output_low>;
> };
> };
> +
> + ir-receiver {
> + ir_recv_pin: ir-recv-pin {
> + rockchip,pins = <RK_GPIO0 10 RK_FUNC_GPIO
&pcfg_pull_none>;
> + };
> + };
> };
>
> };
next prev parent reply other threads:[~2014-07-13 12:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-13 12:10 [PATCH] ARM: dts: rk3188-radxarock: add GPIO IR receiver node Beniamino Galvani
2014-07-13 12:37 ` Heiko Stübner [this message]
2014-07-14 19:04 ` Beniamino Galvani
2014-07-22 21:45 ` Heiko Stübner
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=2390327.HZxnbJmfOO@diego \
--to=heiko@sntech.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