Commit 8996a69c authored by Andy Shevchenko's avatar Andy Shevchenko Committed by Greg Kroah-Hartman

pinctrl: Flag strict is a field in struct pinmux_ops

commit 7440926e upstream.

Documentation incorrectly refers to struct pinctrl_desc, where no such flag is
available. Replace the name of the struct.

Fixes: commit 8c4c2016 ("pinctrl: move strict option to pinmux_ops")
Signed-off-by: default avatarAndy Shevchenko <andriy.shevchenko@linux.intel.com>
Signed-off-by: default avatarLinus Walleij <linus.walleij@linaro.org>
Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
parent 2857aac4
...@@ -831,7 +831,7 @@ separate memory range only intended for GPIO driving, and the register ...@@ -831,7 +831,7 @@ separate memory range only intended for GPIO driving, and the register
range dealing with pin config and pin multiplexing get placed into a range dealing with pin config and pin multiplexing get placed into a
different memory range and a separate section of the data sheet. different memory range and a separate section of the data sheet.
A flag "strict" in struct pinctrl_desc is available to check and deny A flag "strict" in struct pinmux_ops is available to check and deny
simultaneous access to the same pin from GPIO and pin multiplexing simultaneous access to the same pin from GPIO and pin multiplexing
consumers on hardware of this type. The pinctrl driver should set this flag consumers on hardware of this type. The pinctrl driver should set this flag
accordingly. accordingly.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment