pinctrl: remove doc mention of the enable/disable API

This API has changed in commit 6e5e959dde (pinctrl: API changes to support
multiple states per device).

Fixes: 6e5e959dde ('pinctrl: API changes to support multiple states per device')
Cc: Stephen Warren <swarren@nvidia.com>
Signed-off-by: Baruch Siach <baruch@tkos.co.il>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
This commit is contained in:
Baruch Siach 2015-03-08 10:51:46 +02:00 committed by Linus Walleij
parent 260463d492
commit b18104c000
1 changed files with 4 additions and 3 deletions

View File

@ -1264,7 +1264,7 @@ The semantics of the pinctrl APIs are:
Usually the pin control core handled the get/put pair and call out to the Usually the pin control core handled the get/put pair and call out to the
device drivers bookkeeping operations, like checking available functions and 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 driver which takes care of activating and/or deactivating the mux setting by
quickly poking some registers. quickly poking some registers.
@ -1361,8 +1361,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 "Advanced mapping" above. So that for an SPI device, we have two states named
"pos-A" and "pos-B". "pos-A" and "pos-B".
This snippet first muxes the function in the pins defined by group A, enables This snippet first initializes a state object for both groups (in foo_probe()),
it, disables and releases it, and muxes it in on the pins defined by group B: 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> #include <linux/pinctrl/consumer.h>