From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Ruppert Subject: [PATCH] Add a short note on pinctrl_get_group_pins to pinctrl.txt Date: Wed, 16 Oct 2013 14:56:54 +0200 Message-ID: <1381928214-20916-1-git-send-email-christian.ruppert@abilis.com> References: Return-path: In-Reply-To: Sender: linux-doc-owner@vger.kernel.org To: Linus Walleij Cc: Stephen Warren , Patrice CHOTARD , linux-kernel@vger.kernel.org, Grant Likely , Rob Herring , Rob Landley , Sascha Leuenberger , Pierrick Hascoet , linux-doc@vger.kernel.org, Alexandre Courbot , devicetree@vger.kernel.org, Christian Ruppert List-Id: devicetree@vger.kernel.org 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 --- Documentation/pinctrl.txt | 7 ++++++- 1 files changed, 6 insertions(+), 1 deletions(-) diff --git a/Documentation/pinctrl.txt b/Documentation/pinctrl.txt index c0ffd30..a7929cb 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 -- 1.7.1