From: Jisheng Zhang <jszhang@marvell.com>
To: sebastian.hesselbarth@gmail.com, linus.walleij@linaro.org,
antoine.tenart@free-electrons.com
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
pawel.moll@arm.com, ijc+devicetree@hellion.org.uk,
catalin.marinas@arm.com, will.deacon@arm.com,
linux-kernel@vger.kernel.org, Jisheng Zhang <jszhang@marvell.com>,
linux-gpio@vger.kernel.org, robh+dt@kernel.org,
galak@codeaurora.org, linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 6/7] arm64: dts: berlin4ct: add the pinctrl node
Date: Fri, 9 Oct 2015 19:56:49 +0800 [thread overview]
Message-ID: <1444391810-5045-7-git-send-email-jszhang@marvell.com> (raw)
In-Reply-To: <1444391810-5045-1-git-send-email-jszhang@marvell.com>
Add the avio, soc, sm pinctrl nodes for Marvell berlin4ct SoC.
Signed-off-by: Jisheng Zhang <jszhang@marvell.com>
---
arch/arm64/boot/dts/marvell/berlin4ct.dtsi | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/arch/arm64/boot/dts/marvell/berlin4ct.dtsi b/arch/arm64/boot/dts/marvell/berlin4ct.dtsi
index a3b5f1d..8e66355 100644
--- a/arch/arm64/boot/dts/marvell/berlin4ct.dtsi
+++ b/arch/arm64/boot/dts/marvell/berlin4ct.dtsi
@@ -225,6 +225,16 @@
};
};
+ soc_pinctrl: pin-controller@ea8000 {
+ compatible = "marvell,berlin4ct-soc-pinctrl";
+ reg = <0xea8000 0x14>;
+ };
+
+ avio_pinctrl: pin-controller@ea8400 {
+ compatible = "marvell,berlin4ct-avio-pinctrl";
+ reg = <0xea8400 0x8>;
+ };
+
apb@fc0000 {
compatible = "simple-bus";
#address-cells = <1>;
@@ -280,5 +290,10 @@
status = "disabled";
};
};
+
+ system_pinctrl: pin-controller@fe2200 {
+ compatible = "marvell,berlin4ct-system-pinctrl";
+ reg = <0xfe2200 0xc>;
+ };
};
};
--
2.6.1
next prev parent reply other threads:[~2015-10-09 11:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 11:56 [PATCH v5 0/7] arm64: berlin: add pinctrl support Jisheng Zhang
2015-10-09 11:56 ` [PATCH v5 1/7] pinctrl: berlin: introduce berlin_pinctrl_probe_regmap() Jisheng Zhang
[not found] ` <1444391810-5045-1-git-send-email-jszhang-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>
2015-10-09 11:56 ` [PATCH v5 2/7] pinctrl: berlin: Make berlin pinctrl driver visible if COMPILE_TEST=y Jisheng Zhang
2015-10-09 11:56 ` [PATCH v5 3/7] pinctrl: berlin: add the berlin4ct pinctrl driver Jisheng Zhang
2015-10-15 21:52 ` Sebastian Hesselbarth
2015-10-09 11:56 ` [PATCH v5 4/7] arm64: berlin: add the pinctrl dependency for Marvell Berlin SoCs Jisheng Zhang
2015-10-09 11:56 ` [PATCH v5 5/7] pinctrl: dt-binding: document berlin4ct SoC pinctrl Jisheng Zhang
2015-10-09 11:56 ` Jisheng Zhang [this message]
2015-10-09 11:56 ` [PATCH v5 7/7] arm64: dts: berlin4ct: add default pinmux for uart0 Jisheng Zhang
2015-10-10 22:36 ` [PATCH v5 0/7] arm64: berlin: add pinctrl support Antoine Tenart
2015-10-12 2:39 ` Jisheng Zhang
2015-10-10 22:40 ` Antoine Tenart
2015-10-15 21:55 ` Sebastian Hesselbarth
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=1444391810-5045-7-git-send-email-jszhang@marvell.com \
--to=jszhang@marvell.com \
--cc=antoine.tenart@free-electrons.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=will.deacon@arm.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).