Re: Device probing proceeds even when the default pinctrl state is invalid

2016-02-19 Thread Ludovic Desroches
Hi Romain, On Fri, Feb 19, 2016 at 02:30:49PM +0100, romain izard wrote: > 2016-02-18 21:07 GMT+01:00 Linus Walleij : > > On Thu, Feb 18, 2016 at 11:37 AM, Romain Izard > > wrote: > > > >> The current code for device probing tries to map the

Re: Device probing proceeds even when the default pinctrl state is invalid

2016-02-19 Thread Ludovic Desroches
Hi Romain, On Fri, Feb 19, 2016 at 02:30:49PM +0100, romain izard wrote: > 2016-02-18 21:07 GMT+01:00 Linus Walleij : > > On Thu, Feb 18, 2016 at 11:37 AM, Romain Izard > > wrote: > > > >> The current code for device probing tries to map the default pinctrl > >> state (in pinctrl_bind_pins), but

Re: Device probing proceeds even when the default pinctrl state is invalid

2016-02-19 Thread romain izard
2016-02-18 21:07 GMT+01:00 Linus Walleij : > On Thu, Feb 18, 2016 at 11:37 AM, Romain Izard > wrote: > >> The current code for device probing tries to map the default pinctrl >> state (in pinctrl_bind_pins), but is returning 0 or -EDEFER. If

Re: Device probing proceeds even when the default pinctrl state is invalid

2016-02-19 Thread romain izard
2016-02-18 21:07 GMT+01:00 Linus Walleij : > On Thu, Feb 18, 2016 at 11:37 AM, Romain Izard > wrote: > >> The current code for device probing tries to map the default pinctrl >> state (in pinctrl_bind_pins), but is returning 0 or -EDEFER. If there >> is an other error, it is not reported. This

Re: Device probing proceeds even when the default pinctrl state is invalid

2016-02-18 Thread Linus Walleij
On Thu, Feb 18, 2016 at 11:37 AM, Romain Izard wrote: > The current code for device probing tries to map the default pinctrl > state (in pinctrl_bind_pins), but is returning 0 or -EDEFER. If there > is an other error, it is not reported. This means that devices that

Re: Device probing proceeds even when the default pinctrl state is invalid

2016-02-18 Thread Linus Walleij
On Thu, Feb 18, 2016 at 11:37 AM, Romain Izard wrote: > The current code for device probing tries to map the default pinctrl > state (in pinctrl_bind_pins), but is returning 0 or -EDEFER. If there > is an other error, it is not reported. This means that devices that do > not have any specified

Device probing proceeds even when the default pinctrl state is invalid

2016-02-18 Thread Romain Izard
Hello Linus, The current code for device probing tries to map the default pinctrl state (in pinctrl_bind_pins), but is returning 0 or -EDEFER. If there is an other error, it is not reported. This means that devices that do not have any specified pinctrl state can be probed, which is a correct

Device probing proceeds even when the default pinctrl state is invalid

2016-02-18 Thread Romain Izard
Hello Linus, The current code for device probing tries to map the default pinctrl state (in pinctrl_bind_pins), but is returning 0 or -EDEFER. If there is an other error, it is not reported. This means that devices that do not have any specified pinctrl state can be probed, which is a correct