diff mbox

[2/2] pinctrl: remove doc mention of the enable/disable API

Message ID 46f7c40cdc176e60aa4735b9cd515942fec1f7f7.1425804706.git.baruch@tkos.co.il
State New
Headers show

Commit Message

Baruch Siach March 8, 2015, 8:51 a.m. UTC 
This API has changed in commit 6e5e959dde0 (pinctrl: API changes to support
multiple states per device).

Fixes: 6e5e959dde0 ('pinctrl: API changes to support multiple states per device')
Cc: Stephen Warren <swarren@nvidia.com>
Signed-off-by: Baruch Siach <baruch@tkos.co.il>
---
 Documentation/pinctrl.txt | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

Comments

Linus Walleij March 10, 2015, 7:54 a.m. UTC | #1 
On Sun, Mar 8, 2015 at 9:51 AM, Baruch Siach <baruch@tkos.co.il> wrote:

> This API has changed in commit 6e5e959dde0 (pinctrl: API changes to support
> multiple states per device).
>
> Fixes: 6e5e959dde0 ('pinctrl: API changes to support multiple states per device')
> Cc: Stephen Warren <swarren@nvidia.com>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>

Patch applied.

Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
diff mbox

Patch

diff --git a/Documentation/pinctrl.txt b/Documentation/pinctrl.txt
index 91ea46b89d83..2db41b41225e 100644
--- a/Documentation/pinctrl.txt
+++ b/Documentation/pinctrl.txt
@@ -1265,7 +1265,7 @@  The semantics of the pinctrl APIs are:
 
 Usually the pin control core handled the get/put pair and call out to the
 device drivers bookkeeping operations, like checking available functions and
-the associated pins, whereas the enable/disable pass on to the pin controller
+the associated pins, whereas select_state pass on to the pin controller
 driver which takes care of activating and/or deactivating the mux setting by
 quickly poking some registers.
 
@@ -1362,8 +1362,9 @@  function, but with different named in the mapping as described under
 "Advanced mapping" above. So that for an SPI device, we have two states named
 "pos-A" and "pos-B".
 
-This snippet first muxes the function in the pins defined by group A, enables
-it, disables and releases it, and muxes it in on the pins defined by group B:
+This snippet first initializes a state object for both groups (in foo_probe()),
+then muxes the function in the pins defined by group A, and finally muxes it in
+on the pins defined by group B:
 
 #include <linux/pinctrl/consumer.h>