From: Jun Nie <jun.nie@linaro.org>
To: linus.walleij@linaro.org, linux-gpio@vger.kernel.org
Cc: shawn.guo@linaro.org, jason.liu@linaro.org, Jun Nie <jun.nie@linaro.org>
Subject: [PATCH 2/3] pinctrl: zx: Add ZTE pinctrl dts document
Date: Fri, 26 Aug 2016 20:19:24 +0800 [thread overview]
Message-ID: <1472213965-4899-1-git-send-email-jun.nie@linaro.org> (raw)
Add initial ZTE pinctrl dts document for ZX296718 SoC.
Signed-off-by: Jun Nie <jun.nie@linaro.org>
---
.../devicetree/bindings/pinctrl/pinctrl-zx.txt | 54 ++++++++++++++++++++++
1 file changed, 54 insertions(+)
create mode 100644 Documentation/devicetree/bindings/pinctrl/pinctrl-zx.txt
diff --git a/Documentation/devicetree/bindings/pinctrl/pinctrl-zx.txt b/Documentation/devicetree/bindings/pinctrl/pinctrl-zx.txt
new file mode 100644
index 0000000..4061f51
--- /dev/null
+++ b/Documentation/devicetree/bindings/pinctrl/pinctrl-zx.txt
@@ -0,0 +1,54 @@
+* ZTE ZX Pin Controller
+
+The pins controlled by ZX pin controller are organized in banks,
+number of pins in each bank may vary. Each pin has different multiplexing
+functions. There are two type of pins, normal ones and AON ones. AON
+pins control high level multiplex and normal pins may require multiplex
+configuration of parent AON pins. As the AON pins number is not as much as
+normal pins, some normal pins are not routed through AON pin side and are
+under direct control by itself.
+
+Required properties:
+- compatible:
+ "zte,zx296718-pinctrl"
+ "zte,zx296718-aonpmx"
+
+- reg: Should contain the register physical address and length for the
+ pin controller.
+
+IO pull up/down etc configuration is supported with unified management of
+normal pins and AON pins. The configuration registers area is just after
+AON pinmux reg area, while normal pins regs in different area. So two dts
+nodes are needed to provides the two reg regions.
+
+Below configuration are supported. Please refer to pinctrl-bindings.txt
+in this directory for more details of the common pinctrl bindings used
+by client devices.
+
+bias-pull-up - pull up the pin
+bias-pull-down - pull down the pin
+drive-strength - sink or source at most 7 mA
+input-enable - enable input on pin (no effect on output)
+power-source - select power supplies. 1: 1.8V, 0: 3.3V
+slew-rate - set the slew rate
+
+Pin names are defined by bank sequence and pins number in the bank. For
+example, B2 is the 3rd pin in the second bank. The AON pin has prefix
+AON, like AONC2.
+
+Example dts nodes:
+
+pinctop: pinctrl@01462000 {
+ compatible = "zte,zx296718-pinctrl";
+ reg = <0x01462000 0x1000>;
+
+ i2c5_pins: i2c5pins {
+ pins = "G6", "G7";
+ function = "I2C5";
+ }
+};
+
+pmx_aon: pinctrl@00119000 {
+ compatible = "zte,zx296718-aonpmx";
+ reg = <0x00119000 0x1000>;
+};
--
1.9.1
next reply other threads:[~2016-08-26 12:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 12:19 Jun Nie [this message]
2016-08-26 12:19 ` [PATCH 3/3] pinctrl: zx: Add ZTE ZX SoC pinctrl driver Jun Nie
2016-09-06 14:31 ` Linus Walleij
2016-09-07 4:45 ` Jun Nie
[not found] ` <1472213965-4899-1-git-send-email-jun.nie-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-09-06 14:15 ` [PATCH 2/3] pinctrl: zx: Add ZTE pinctrl dts document Linus Walleij
[not found] ` <CACRpkdZ5aHJs8EK29_y7wYZhyHAUdD99wy2RRGD-CZdoJo+NrA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-09-06 14:43 ` Linus Walleij
2016-09-07 4:07 ` Jun Nie
2016-09-07 3:40 ` Jun Nie
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=1472213965-4899-1-git-send-email-jun.nie@linaro.org \
--to=jun.nie@linaro.org \
--cc=jason.liu@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=shawn.guo@linaro.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).