From: djw@t-chip.com.cn
To: linux-rockchip@lists.infradead.org
Cc: Wayne Chou <zxf@t-chip.com.cn>, Levin Du <djw@t-chip.com.cn>,
Heiko Stuebner <heiko@sntech.de>,
devicetree@vger.kernel.org, David Wu <david.wu@rock-chips.com>,
Arnd Bergmann <arnd@arndb.de>,
Finley Xiao <finley.xiao@rock-chips.com>,
William Wu <william.wu@rock-chips.com>,
Sugar Zhang <sugar.zhang@rock-chips.com>,
linux-kernel@vger.kernel.org, Robin Murphy <robin.murphy@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Rocky Hao <rocky.hao@rock-chips.com>,
Will Deacon <will.deacon@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 3/5] arm64: dts: rockchip: Add GPIO_MUTE pin support to rk3328
Date: Thu, 31 May 2018 11:27:51 +0800 [thread overview]
Message-ID: <1527737273-8387-4-git-send-email-djw@t-chip.com.cn> (raw)
In-Reply-To: <1527737273-8387-1-git-send-email-djw@t-chip.com.cn>
From: Levin Du <djw@t-chip.com.cn>
Adding a new gpio controller named "gpio_mute" to rk3328, providing
access to the GPIO_MUTE pin, which is manupulated by the GRF_SOC_CON10
register.
The GPIO_MUTE pin is referred to as <&gpio_mute 0>.
Signed-off-by: Levin Du <djw@t-chip.com.cn>
---
Changes in v3:
- Use dedicated "rockchip,rk3328-gpio-mute" driver
Changes in v2:
- Rename gpio_syscon10 to gpio_mute in rk3328.dtsi
Changes in v1:
- Split from V0 and add to rk3328.dtsi for general use.
arch/arm64/boot/dts/rockchip/rk3328.dtsi | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/arch/arm64/boot/dts/rockchip/rk3328.dtsi b/arch/arm64/boot/dts/rockchip/rk3328.dtsi
index be2bfbc..2ee0fa3 100644
--- a/arch/arm64/boot/dts/rockchip/rk3328.dtsi
+++ b/arch/arm64/boot/dts/rockchip/rk3328.dtsi
@@ -309,6 +309,13 @@
mode-loader = <BOOT_BL_DOWNLOAD>;
};
+ /* Use <&gpio_mute 0> to refer to GPIO_MUTE pin */
+ gpio_mute: gpio-mute {
+ compatible = "rockchip,rk3328-gpio-mute";
+ gpio-controller;
+ #gpio-cells = <2>;
+ status = "disabled";
+ };
};
uart0: serial@ff110000 {
--
2.7.4
next prev parent reply other threads:[~2018-05-31 3:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 3:27 [PATCH v3 0/5] Add sdmmc UHS support to ROC-RK3328-CC board djw
2018-05-31 3:27 ` [PATCH v3 1/5] gpio: syscon: allow fetching syscon from parent node djw
2018-06-08 7:54 ` Linus Walleij
2018-05-31 3:27 ` [PATCH v3 2/5] gpio: syscon: rockchip: add GPIO_MUTE support for rk3328 djw
2018-05-31 14:45 ` Rob Herring
2018-06-01 2:05 ` Levin
2018-06-01 17:03 ` Rob Herring
2018-06-02 8:40 ` Levin Du
2018-06-05 19:58 ` Rob Herring
2018-06-07 1:32 ` Levin
2018-06-28 7:22 ` djw
2018-07-06 21:10 ` Rob Herring
2018-05-31 3:27 ` djw [this message]
2018-05-31 3:27 ` [PATCH v3 4/5] arm64: dts: rockchip: Add io-domain to roc-rk3328-cc djw
2018-05-31 5:03 ` [PATCH v3 5/5] arm64: dts: rockchip: Add sdmmc UHS support for roc-rk3328-cc djw
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=1527737273-8387-4-git-send-email-djw@t-chip.com.cn \
--to=djw@t-chip.com.cn \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=david.wu@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=finley.xiao@rock-chips.com \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=rocky.hao@rock-chips.com \
--cc=sugar.zhang@rock-chips.com \
--cc=will.deacon@arm.com \
--cc=william.wu@rock-chips.com \
--cc=zxf@t-chip.com.cn \
/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).