Re: [PATCH fixes v4] pinctrl: Do not check previous and current state

2017-03-15 Thread Linus Walleij
On Mon, Mar 13, 2017 at 8:06 PM, Andy Shevchenko wrote: > On Mon, Mar 13, 2017 at 8:59 PM, Florian Fainelli > wrote: >> On 03/07/2017 10:52 AM, Florian Fainelli wrote: > >> Linus am I hitting some of your spam folder, or you are really having >> way too much fun with Gemini ;) ? > > A bit offtop

Re: [PATCH fixes v4] pinctrl: Do not check previous and current state

2017-03-15 Thread Linus Walleij
On Tue, Mar 7, 2017 at 7:52 PM, Florian Fainelli wrote: > In case a platform only defaults a "default" set of pins, but not a > "sleep" set of pins, and this particular platform suspends and resumes > in a way that the pin states are not preserved by the hardware, when we > resume, we would call

Re: [PATCH fixes v4] pinctrl: Do not check previous and current state

2017-03-13 Thread Andy Shevchenko
On Mon, Mar 13, 2017 at 8:59 PM, Florian Fainelli wrote: > On 03/07/2017 10:52 AM, Florian Fainelli wrote: > Linus am I hitting some of your spam folder, or you are really having > way too much fun with Gemini ;) ? A bit offtopic here, but I have almost same question. I noticed no reaction for p

Re: [PATCH fixes v4] pinctrl: Do not check previous and current state

2017-03-13 Thread Florian Fainelli
On 03/07/2017 10:52 AM, Florian Fainelli wrote: > In case a platform only defaults a "default" set of pins, but not a > "sleep" set of pins, and this particular platform suspends and resumes > in a way that the pin states are not preserved by the hardware, when we > resume, we would call pinctrl_si

[PATCH fixes v4] pinctrl: Do not check previous and current state

2017-03-07 Thread Florian Fainelli
In case a platform only defaults a "default" set of pins, but not a "sleep" set of pins, and this particular platform suspends and resumes in a way that the pin states are not preserved by the hardware, when we resume, we would call pinctrl_single_resume() -> pinctrl_force_default() -> pinctrl_sele