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:
@@ -114,8 +114,6 @@ struct pinctrl_ops {
|
||||
* of the pins field above
|
||||
* @pctlops: pin control operation vtable, to support global concepts like
|
||||
* grouping of pins, this is optional.
|
||||
* @strict: check both gpio_owner and mux_owner strictly before approving
|
||||
the pin request
|
||||
* @pmxops: pinmux operations vtable, if you support pinmuxing in your driver
|
||||
* @confops: pin config operations vtable, if you support pin configuration in
|
||||
* your driver
|
||||
@@ -134,7 +132,6 @@ struct pinctrl_desc {
|
||||
const struct pinctrl_ops *pctlops;
|
||||
const struct pinmux_ops *pmxops;
|
||||
const struct pinconf_ops *confops;
|
||||
bool strict;
|
||||
struct module *owner;
|
||||
#ifdef CONFIG_GENERIC_PINCONF
|
||||
unsigned int num_custom_params;
|
||||
|
Reference in New Issue
Block a user