From: Andrew Jeffery <andrew@aj.id.au>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Andrew Jeffery <andrew@aj.id.au>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Lee Jones <lee.jones@linaro.org>, Joel Stanley <joel@jms.id.au>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v4 1/5] pinctrl: aspeed: dt: Fix compatibles for the System Control Unit
Date: Tue, 20 Dec 2016 18:05:47 +1030 [thread overview]
Message-ID: <20161220073551.28522-2-andrew@aj.id.au> (raw)
In-Reply-To: <20161220073551.28522-1-andrew@aj.id.au>
Reference the SoC-specific compatible string in the examples as
required.
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
---
Documentation/devicetree/bindings/pinctrl/pinctrl-aspeed.txt | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/Documentation/devicetree/bindings/pinctrl/pinctrl-aspeed.txt b/Documentation/devicetree/bindings/pinctrl/pinctrl-aspeed.txt
index 2ad18c4ea55c..b2efb73337c6 100644
--- a/Documentation/devicetree/bindings/pinctrl/pinctrl-aspeed.txt
+++ b/Documentation/devicetree/bindings/pinctrl/pinctrl-aspeed.txt
@@ -11,9 +11,14 @@ Required properties:
"aspeed,ast2500-pinctrl"
"aspeed,g5-pinctrl"
-The pin controller node should be a child of a syscon node with the required
+The pin controller node should be the child of a syscon node with the required
property:
-- compatible: "syscon", "simple-mfd"
+
+- compatible : Should be one of the following:
+ "aspeed,ast2400-scu", "syscon", "simple-mfd"
+ "aspeed,g4-scu", "syscon", "simple-mfd"
+ "aspeed,ast2500-scu", "syscon", "simple-mfd"
+ "aspeed,g5-scu", "syscon", "simple-mfd"
Refer to the the bindings described in
Documentation/devicetree/bindings/mfd/syscon.txt
@@ -50,7 +55,7 @@ TIMER7 TIMER8 VGABIOSROM
Examples:
syscon: scu@1e6e2000 {
- compatible = "syscon", "simple-mfd";
+ compatible = "aspeed,ast2400-scu", "syscon", "simple-mfd";
reg = <0x1e6e2000 0x1a8>;
pinctrl: pinctrl {
--
2.9.3
next prev parent reply other threads:[~2016-12-20 7:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-20 7:35 [PATCH v4 0/5] pinctrl: aspeed: Implement remaining pins Andrew Jeffery
2016-12-20 7:35 ` Andrew Jeffery [this message]
2016-12-20 7:56 ` [PATCH v4 1/5] pinctrl: aspeed: dt: Fix compatibles for the System Control Unit Joel Stanley
[not found] ` <20161220073551.28522-2-andrew-zrmu5oMJ5Fs@public.gmane.org>
2016-12-22 21:01 ` Rob Herring
2016-12-27 22:14 ` Linus Walleij
2016-12-20 7:35 ` [PATCH v4 2/5] pinctrl: aspeed: Read and write bits in LPC and GFX controllers Andrew Jeffery
[not found] ` <20161220073551.28522-3-andrew-zrmu5oMJ5Fs@public.gmane.org>
2016-12-22 21:03 ` Rob Herring
2016-12-27 22:16 ` Linus Walleij
2016-12-20 7:35 ` [PATCH v4 3/5] pinctrl: aspeed-g4: Add mux configuration for all pins Andrew Jeffery
2016-12-27 22:18 ` Linus Walleij
2016-12-20 7:35 ` [PATCH v4 4/5] pinctrl: aspeed-g5: " Andrew Jeffery
[not found] ` <20161220073551.28522-5-andrew-zrmu5oMJ5Fs@public.gmane.org>
2016-12-28 0:22 ` Linus Walleij
2016-12-20 7:35 ` [PATCH v4 5/5] pinctrl: aspeed: Fix kerneldoc return descriptions Andrew Jeffery
2016-12-28 0:23 ` Linus Walleij
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=20161220073551.28522-2-andrew@aj.id.au \
--to=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).