summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorChristian Ruppert <christian.ruppert@abilis.com>2013-10-16 14:56:54 +0200
committerLinus Walleij <linus.walleij@linaro.org>2013-10-16 15:35:21 +0200
commitfe61052ae97a33c229a3ae7ad29e0c9b9ccada02 (patch)
treea494037cd453302904667be243121b03ab9625bd /Documentation
parent5a92750133ffd998e92e4f7ed874fae61d67aeed (diff)
pinctrl: add documentation for pinctrl_get_group_pins()
This patch adds a short description of how to use the newly added pinctrl_get_group_pins function to the pinctrl documentation. Signed-off-by: Christian Ruppert <christian.ruppert@abilis.com> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/pinctrl.txt7
1 files changed, 6 insertions, 1 deletions
diff --git a/Documentation/pinctrl.txt b/Documentation/pinctrl.txt
index c0ffd30eb55e..a7929cb47e7c 100644
--- a/Documentation/pinctrl.txt
+++ b/Documentation/pinctrl.txt
@@ -358,7 +358,12 @@ static struct pinctrl_gpio_range gpio_range = {
.gc = &chip;
};
-In this case the pin_base property will be ignored.
+In this case the pin_base property will be ignored. If the name of a pin
+group is known, the pins and npins elements of the above structure can be
+initialised using the function pinctrl_get_group_pins(), e.g. for pin
+group "foo":
+
+pinctrl_get_group_pins(pctl, "foo", &gpio_range.pins, &gpio_range.npins);
When GPIO-specific functions in the pin control subsystem are called, these
ranges will be used to look up the appropriate pin controller by inspecting