[PATCH 4.7 017/141] pinctrl: Flag strict is a field in struct pinmux_ops

From: Greg Kroah-Hartman
Date: Thu Oct 06 2016 - 04:33:29 EST

4.7-stable review patch. If anyone has any objections, please let me know.


From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>

commit 7440926ed9623dceca3310c5f437d06c859dc02b upstream.

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

Fixes: commit 8c4c2016345f ("pinctrl: move strict option to pinmux_ops")
Signed-off-by: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
Signed-off-by: Linus Walleij <linus.walleij@xxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>

Documentation/pinctrl.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

--- a/Documentation/pinctrl.txt
+++ b/Documentation/pinctrl.txt
@@ -831,7 +831,7 @@ separate memory range only intended for
range dealing with pin config and pin multiplexing get placed into a
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
consumers on hardware of this type. The pinctrl driver should set this flag