From: Jisheng Zhang <jszhang@marvell.com>
To: sebastian.hesselbarth@gmail.com, linus.walleij@linaro.org,
antoine.tenart@free-electrons.com
Cc: catalin.marinas@arm.com, will.deacon@arm.com,
mark.rutland@arm.com, robh+dt@kernel.org, pawel.moll@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Jisheng Zhang <jszhang@marvell.com>
Subject: [PATCH v5 5/7] pinctrl: dt-binding: document berlin4ct SoC pinctrl
Date: Fri, 9 Oct 2015 19:56:48 +0800 [thread overview]
Message-ID: <1444391810-5045-6-git-send-email-jszhang@marvell.com> (raw)
In-Reply-To: <1444391810-5045-1-git-send-email-jszhang@marvell.com>
Add berlin4ct to existing berlin pinctrl device tree binding.
Signed-off-by: Jisheng Zhang <jszhang@marvell.com>
---
Documentation/devicetree/bindings/pinctrl/berlin,pinctrl.txt | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/pinctrl/berlin,pinctrl.txt b/Documentation/devicetree/bindings/pinctrl/berlin,pinctrl.txt
index a8bb5e2..f8fa28c 100644
--- a/Documentation/devicetree/bindings/pinctrl/berlin,pinctrl.txt
+++ b/Documentation/devicetree/bindings/pinctrl/berlin,pinctrl.txt
@@ -20,7 +20,10 @@ Required properties:
"marvell,berlin2cd-soc-pinctrl",
"marvell,berlin2cd-system-pinctrl",
"marvell,berlin2q-soc-pinctrl",
- "marvell,berlin2q-system-pinctrl"
+ "marvell,berlin2q-system-pinctrl",
+ "marvell,berlin4ct-avio-pinctrl",
+ "marvell,berlin4ct-soc-pinctrl",
+ "marvell,berlin4ct-system-pinctrl"
Required subnode-properties:
- groups: a list of strings describing the group names.
--
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 ` Jisheng Zhang [this message]
2015-10-09 11:56 ` [PATCH v5 6/7] arm64: dts: berlin4ct: add the pinctrl node Jisheng Zhang
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-6-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).