mirror of
https://github.com/torvalds/linux.git
synced 2026-05-28 09:04:39 +02:00
pinctrl: pinmux: Add missing .function_is_gpio kerneldoc
This callback was undocumented, add the docs. Reviewed-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
This commit is contained in:
parent
a419bc0f13
commit
7958b4bb80
|
|
@ -35,6 +35,16 @@ struct pinctrl_gpio_range;
|
|||
* name can be used with the generic @pinctrl_ops to retrieve the
|
||||
* actual pins affected. The applicable groups will be returned in
|
||||
* @groups and the number of groups in @num_groups
|
||||
* @function_is_gpio: determine if the indicated function selector passed
|
||||
* corresponds to the GPIO function which is used by the accelerated GPIO
|
||||
* functions @gpio_request_enable, @gpio_disable_free and
|
||||
* @gpio_set_direction. When the pin control core can properly determine
|
||||
* if a function is a GPIO function, it is easier to use the @strict mode
|
||||
* on the pin controller. Since a single function is passed, this is
|
||||
* only useful on pin controllers that use a specific function for GPIO,
|
||||
* and that usually presupposes that a one-group-per-pin approach is
|
||||
* used, so that a single function can be set on a single pin to turn
|
||||
* it to GPIO mode.
|
||||
* @set_mux: enable a certain muxing function with a certain pin group. The
|
||||
* driver does not need to figure out whether enabling this function
|
||||
* conflicts some other use of the pins in that group, such collisions
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user