pinctrl: move strict option to pinmux_ops
While the pinmux_ops are ideally just a vtable for pin mux calls, the "strict" setting belongs so intuitively with the pin multiplexing that we should move it here anyway. Putting it in the top pinctrl_desc makes no sense. Cc: Sonic Zhang <sonic.zhang@analog.com> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
This commit is contained in:
@@ -56,6 +56,9 @@ struct pinctrl_dev;
|
||||
* depending on whether the GPIO is configured as input or output,
|
||||
* a direction selector function may be implemented as a backing
|
||||
* to the GPIO controllers that need pin muxing.
|
||||
* @strict: do not allow simultaneous use of the same pin for GPIO and another
|
||||
* function. Check both gpio_owner and mux_owner strictly before approving
|
||||
* the pin request.
|
||||
*/
|
||||
struct pinmux_ops {
|
||||
int (*request) (struct pinctrl_dev *pctldev, unsigned offset);
|
||||
@@ -79,6 +82,7 @@ struct pinmux_ops {
|
||||
struct pinctrl_gpio_range *range,
|
||||
unsigned offset,
|
||||
bool input);
|
||||
bool strict;
|
||||
};
|
||||
|
||||
#endif /* CONFIG_PINMUX */
|
||||
|
Reference in New Issue
Block a user