Re: [PATCH v1 1/1] pinctrl: Flag strict is a field in struct pinmux_ops

[Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>]

On Tue, 2016-06-21 at 01:40 +0300, Andy Shevchenko wrote:
> 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>
> ---
>  Documentation/pinctrl.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/pinctrl.txt b/Documentation/pinctrl.txt
> index 4976389e..dd15a69 100644
> --- a/Documentation/pinctrl.txt
> +++ b/Documentation/pinctrl.txt
> @@ -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
>  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
>  accordingly.

-- 

Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
Intel Finland Oy
--
To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html