From: Oleksij Rempel <linux@rempel-privat.de>
To: linus.walleij@linaro.org, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Oleksij Rempel <linux@rempel-privat.de>
Subject: [PATCH v2 2/2] pinctrl: asm9260: add pinctrl add device tree bindings documentation
Date: Fri, 27 Mar 2015 10:36:13 +0100 [thread overview]
Message-ID: <1427448973-665-3-git-send-email-linux@rempel-privat.de> (raw)
In-Reply-To: <1427448973-665-1-git-send-email-linux@rempel-privat.de>
Add device tree bindings documentation for Alphascale asm9260 pin controller
Signed-off-by: Oleksij Rempel <linux@rempel-privat.de>
---
.../pinctrl/alphascale,asm9260-pinctrl.txt | 76 ++++++++++++++++++++++
1 file changed, 76 insertions(+)
create mode 100644 Documentation/devicetree/bindings/pinctrl/alphascale,asm9260-pinctrl.txt
diff --git a/Documentation/devicetree/bindings/pinctrl/alphascale,asm9260-pinctrl.txt b/Documentation/devicetree/bindings/pinctrl/alphascale,asm9260-pinctrl.txt
new file mode 100644
index 0000000..dbeea4d
--- /dev/null
+++ b/Documentation/devicetree/bindings/pinctrl/alphascale,asm9260-pinctrl.txt
@@ -0,0 +1,76 @@
+* Alphascale ASM9260 SoC pinctrl core driver
+
+The pinctrl driver enables Alphascale ASM9260 to configure pin multiplexing
+to a specific function.
+
+Required properties for pinctrl driver:
+- compatible: "alphascale,asm9260-pinctrl"
+- reg: Register base of the MPP block and length.
+- clocks: clock ids.
+- clock-names:
+ * 1 "ahb" : AHB gating clock.
+
+Please refer to pinctrl-bindings.txt in this directory for details of the
+common pinctrl bindings used by client devices, including the meaning of the
+phrase "pin configuration node".
+
+The pin configuration nodes act as a container for an arbitrary number of
+subnodes. Each of these subnodes represents some desired configuration for a
+pin or a list of pins. This configuration can include the
+mux function to select on those pin(s), and various pin configuration
+parameters, as listed below.
+
+SUBNODES:
+
+The name of each subnode is not important; all subnodes should be enumerated
+and processed purely based on their content.
+
+Each subnode only affects those parameters that are explicitly listed. In
+other words, a subnode that lists a mux function but no pin configuration
+parameters implies no information about any pin configuration parameters.
+Similarly, a pin subnode that describes a pullup parameter implies no
+information about e.g. the mux function.
+
+The following generic properties as defined in pinctrl-bindings.txt are valid
+to specify in a pin configuration subnode:
+pins - the list of pins that properties in the node
+ apply to (either this or "groups" has to be
+ specified)
+function - the mux function to select
+bias-disable - disable any pin bias
+bias-pull-up - pull up the pin. Supported only on GPIO0_* pins.
+bias-pull-down - pull down the pin. Supported on all pins except of GPIO0_*.
+
+Examples:
+
+pinctrl: pinctrl@80044000 {
+ compatible = "alphascale,asm9260-pinctrl";
+ reg = <0x80044000 0x400>;
+ clocks = <&acc CLKID_AHB_IOCONFIG>;
+ clock-names = "ahb";
+
+ nand_fc0_pins_a: nand_fc0 {
+ nand_main_gr {
+ pins = "GPIO11_0", "GPIO11_1", "GPIO11_2",
+ "GPIO11_3", "GPIO11_4", "GPIO11_6",
+ "GPIO12_0", "GPIO12_1", "GPIO12_2",
+ "GPIO12_3", "GPIO12_4", "GPIO12_5",
+ "GPIO12_6", "GPIO12_7";
+ function = "nand0";
+ bias-disable;
+ };
+ };
+};
+
+nand_controller0 {
+ status = "okay";
+ #address-cells = <1>;
+ #size-cells = <1>;
+ nand-ecc-strength = <4>;
+ nand-ecc-step-size = <512>;
+ nand-max-chips = <1>;
+ nand-on-flash-bbt;
+
+ pinctrl-names = "default";
+ pinctrl-0 = <&nand_fc0_pins_a>;
+};
--
1.9.1
prev parent reply other threads:[~2015-03-27 9:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACRpkdbKLkMB6WP0zp2xN+gM4ytvs=3V5hh8uKt8e=YE4gAAqQ@mail.gmail.com>
2015-03-27 9:36 ` [PATCH v2 0/2] Add driver and documentation for Alphascale asm9260 pinctrl Oleksij Rempel
2015-03-27 9:36 ` [PATCH v2 1/2] pinctrl: Add driver " Oleksij Rempel
2015-03-27 17:10 ` Paul Bolle
2015-04-05 5:49 ` Oleksij Rempel
2015-04-05 6:16 ` Oleksij Rempel
2015-04-05 6:26 ` [PATCH v3 0/2] Add driver and documentation " Oleksij Rempel
2015-04-05 6:26 ` [PATCH v3 1/2] pinctrl: Add driver " Oleksij Rempel
2015-04-06 7:42 ` Paul Bolle
2015-04-06 8:38 ` Oleksij Rempel
2015-04-06 9:41 ` Paul Bolle
2015-04-06 9:45 ` Oleksij Rempel
2015-04-06 9:04 ` [PATCH v4 0/2] Add driver and documentation " Oleksij Rempel
2015-04-06 9:04 ` [PATCH v4 1/2] pinctrl: Add driver " Oleksij Rempel
2015-05-05 15:12 ` Linus Walleij
2015-05-12 16:25 ` Oleksij Rempel
2015-05-13 11:00 ` Linus Walleij
2015-05-14 7:26 ` Oleksij Rempel
2015-09-09 5:55 ` Oleksij Rempel
2015-09-25 17:14 ` Linus Walleij
2015-04-06 9:04 ` [PATCH v4 2/2] pinctrl: asm9260: add pinctrl add device tree bindings documentation Oleksij Rempel
2015-05-05 14:46 ` Linus Walleij
2015-05-12 16:02 ` Oleksij Rempel
2015-04-22 19:49 ` [PATCH v4 0/2] Add driver and documentation for Alphascale asm9260 pinctrl Oleksij Rempel
2015-05-05 14:41 ` Linus Walleij
[not found] ` <1428215185-14190-1-git-send-email-linux-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org>
2015-04-05 6:26 ` [PATCH v3 2/2] pinctrl: asm9260: add pinctrl add device tree bindings documentation Oleksij Rempel
2015-03-27 9:36 ` Oleksij Rempel [this message]
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=1427448973-665-3-git-send-email-linux@rempel-privat.de \
--to=linux@rempel-privat.de \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.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).