From: Andy Yan <andy.yan@rock-chips.com>
To: robh+dt@kernel.org, heiko@sntech.de, linus.walleij@linaro.org,
devicetree@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Andy Yan <andy.yan@rock-chips.com>
Subject: [PATCH 4/7] dt-bindings: rockchip,pinctrl: rename RK1108 to RV1108
Date: Mon, 13 Feb 2017 19:06:23 +0800 [thread overview]
Message-ID: <1486983983-32506-1-git-send-email-andy.yan@rock-chips.com> (raw)
In-Reply-To: <1486983566-32265-1-git-send-email-andy.yan@rock-chips.com>
Rockchip finally named the SOC as RV1108, so change it.
Also move the compatible list to one compatible per line.
Signed-off-by: Andy Yan <andy.yan@rock-chips.com>
---
.../devicetree/bindings/pinctrl/rockchip,pinctrl.txt | 16 +++++++++++-----
1 file changed, 11 insertions(+), 5 deletions(-)
diff --git a/Documentation/devicetree/bindings/pinctrl/rockchip,pinctrl.txt b/Documentation/devicetree/bindings/pinctrl/rockchip,pinctrl.txt
index 4722bc6..a4f3ef2 100644
--- a/Documentation/devicetree/bindings/pinctrl/rockchip,pinctrl.txt
+++ b/Documentation/devicetree/bindings/pinctrl/rockchip,pinctrl.txt
@@ -19,11 +19,17 @@ The pins are grouped into up to 5 individual pin banks which need to be
defined as gpio sub-nodes of the pinmux controller.
Required properties for iomux controller:
- - compatible: one of "rockchip,rk1108-pinctrl", "rockchip,rk2928-pinctrl"
- "rockchip,rk3066a-pinctrl", "rockchip,rk3066b-pinctrl"
- "rockchip,rk3188-pinctrl", "rockchip,rk3228-pinctrl"
- "rockchip,rk3288-pinctrl", "rockchip,rk3368-pinctrl"
- "rockchip,rk3399-pinctrl"
+ - compatible: should be
+ "rockchip,rv1108-pinctrl": for Rockchip RV1108
+ "rockchip,rk2928-pinctrl": for Rockchip RK2928
+ "rockchip,rk3066a-pinctrl": for Rockchip RK3066a
+ "rockchip,rk3066b-pinctrl": for Rockchip RK3066b
+ "rockchip,rk3188-pinctrl": for Rockchip RK3188
+ "rockchip,rk3228-pinctrl": for Rockchip RK3228
+ "rockchip,rk3288-pinctrl": for Rockchip RK3288
+ "rockchip,rk3368-pinctrl": for Rockchip RK3368
+ "rockchip,rk3399-pinctrl": for Rockchip RK3399
+
- rockchip,grf: phandle referencing a syscon providing the
"general register files"
--
2.7.4
next prev parent reply other threads:[~2017-02-13 11:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1486983566-32265-1-git-send-email-andy.yan@rock-chips.com>
2017-02-13 11:02 ` [PATCH 1/7] dt-bindings: rockchip-dw-mshc: " Andy Yan
2017-02-14 8:51 ` Ulf Hansson
2017-02-21 23:36 ` Rob Herring
2017-02-22 1:51 ` Heiko Stuebner
2017-02-23 14:59 ` Heiko Stuebner
2017-03-14 16:20 ` Ulf Hansson
2017-02-13 11:04 ` [PATCH 2/7] dt-bindings: rk1108-cru: " Andy Yan
2017-02-22 20:47 ` Rob Herring
2017-02-13 11:04 ` [PATCH 3/7] clk: rockchip: " Andy Yan
2017-02-13 11:06 ` Andy Yan [this message]
2017-02-22 15:08 ` [PATCH 4/7] dt-bindings: rockchip,pinctrl: " Rob Herring
2017-02-22 18:33 ` Heiko Stuebner
2017-03-14 13:26 ` Linus Walleij
2017-02-13 11:07 ` [PATCH 5/7] pinctrl: rockchip: " Andy Yan
2017-02-22 18:34 ` Heiko Stuebner
2017-02-13 11:09 ` [PATCH 6/7] ARM: dts: " Andy Yan
2017-02-13 11:10 ` [PATCH 7/7] ARM: rockchip: reanme " Andy Yan
2017-02-22 15:10 ` Rob Herring
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=1486983983-32506-1-git-send-email-andy.yan@rock-chips.com \
--to=andy.yan@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--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
all inboxes | Powered by JetHome®