Re: [PATCH v2 2/2] pinctrl: Allow indicating loss of pin states during low-power

Le 12/19/17 à 23:24, Linus Walleij a écrit : > On Mon, Dec 11, 2017 at 12:38 AM, Florian Fainelli > wrote: >> On 12/02/2017 04:48 AM, Linus Walleij wrote: > >>> This should solve your problem without having to alter the semantics >>> of pinctrl_select_state() for everyone.

Re: [PATCH v2 2/2] pinctrl: Allow indicating loss of pin states during low-power

Le 12/19/17 à 23:24, Linus Walleij a écrit : > On Mon, Dec 11, 2017 at 12:38 AM, Florian Fainelli > wrote: >> On 12/02/2017 04:48 AM, Linus Walleij wrote: > >>> This should solve your problem without having to alter the semantics >>> of pinctrl_select_state() for everyone. >> >> This was

Re: [PATCH v2 2/2] pinctrl: Allow indicating loss of pin states during low-power

On Mon, Dec 11, 2017 at 12:38 AM, Florian Fainelli wrote: > On 12/02/2017 04:48 AM, Linus Walleij wrote: >> This should solve your problem without having to alter the semantics >> of pinctrl_select_state() for everyone. > > This was exactly what I proposed initially here: >

Re: [PATCH v2 2/2] pinctrl: Allow indicating loss of pin states during low-power

On Mon, Dec 11, 2017 at 12:38 AM, Florian Fainelli wrote: > On 12/02/2017 04:48 AM, Linus Walleij wrote: >> This should solve your problem without having to alter the semantics >> of pinctrl_select_state() for everyone. > > This was exactly what I proposed initially here: > >

Re: [PATCH v2 2/2] pinctrl: Allow indicating loss of pin states during low-power

On 12/02/2017 04:48 AM, Linus Walleij wrote: > On Wed, Nov 29, 2017 at 6:37 PM, Florian Fainelli > wrote: >> On 11/29/2017 09:02 AM, Tony Lindgren wrote: > >>> Hmm well typically a device driver that loses it's context just does >>> save and restore of the registers in

Re: [PATCH v2 2/2] pinctrl: Allow indicating loss of pin states during low-power

On 12/02/2017 04:48 AM, Linus Walleij wrote: > On Wed, Nov 29, 2017 at 6:37 PM, Florian Fainelli > wrote: >> On 11/29/2017 09:02 AM, Tony Lindgren wrote: > >>> Hmm well typically a device driver that loses it's context just does >>> save and restore of the registers in runtime PM

Re: [PATCH v2 2/2] pinctrl: Allow indicating loss of pin states during low-power

On Wed, Nov 29, 2017 at 6:37 PM, Florian Fainelli wrote: > On 11/29/2017 09:02 AM, Tony Lindgren wrote: >> Hmm well typically a device driver that loses it's context just does >> save and restore of the registers in runtime PM suspend/resume >> as needed. In this case it

Re: [PATCH v2 2/2] pinctrl: Allow indicating loss of pin states during low-power

On Wed, Nov 29, 2017 at 6:37 PM, Florian Fainelli wrote: > On 11/29/2017 09:02 AM, Tony Lindgren wrote: >> Hmm well typically a device driver that loses it's context just does >> save and restore of the registers in runtime PM suspend/resume >> as needed. In this case it would mean duplicating

Re: [PATCH v2 2/2] pinctrl: Allow indicating loss of pin states during low-power

On 11/29/2017 09:02 AM, Tony Lindgren wrote: > * Linus Walleij [171129 13:03]: >> On Fri, Nov 3, 2017 at 12:15 AM, Florian Fainelli >> wrote: >> >>> Some platforms (e.g: Broadcom STB: BMIPS_GENERIC/ARCH_BRCMSTB) will lose >>> their register

Re: [PATCH v2 2/2] pinctrl: Allow indicating loss of pin states during low-power

On 11/29/2017 09:02 AM, Tony Lindgren wrote: > * Linus Walleij [171129 13:03]: >> On Fri, Nov 3, 2017 at 12:15 AM, Florian Fainelli >> wrote: >> >>> Some platforms (e.g: Broadcom STB: BMIPS_GENERIC/ARCH_BRCMSTB) will lose >>> their register contents when entering their lower power state. In

Re: [PATCH v2 2/2] pinctrl: Allow indicating loss of pin states during low-power

* Linus Walleij [171129 13:03]: > On Fri, Nov 3, 2017 at 12:15 AM, Florian Fainelli > wrote: > > > Some platforms (e.g: Broadcom STB: BMIPS_GENERIC/ARCH_BRCMSTB) will lose > > their register contents when entering their lower power state. In such

Re: [PATCH v2 2/2] pinctrl: Allow indicating loss of pin states during low-power

* Linus Walleij [171129 13:03]: > On Fri, Nov 3, 2017 at 12:15 AM, Florian Fainelli > wrote: > > > Some platforms (e.g: Broadcom STB: BMIPS_GENERIC/ARCH_BRCMSTB) will lose > > their register contents when entering their lower power state. In such a > > case, the pinctrl-single driver that is

Re: [PATCH v2 2/2] pinctrl: Allow indicating loss of pin states during low-power

On Fri, Nov 3, 2017 at 12:15 AM, Florian Fainelli wrote: > Some platforms (e.g: Broadcom STB: BMIPS_GENERIC/ARCH_BRCMSTB) will lose > their register contents when entering their lower power state. In such a > case, the pinctrl-single driver that is used will not be able to

Re: [PATCH v2 2/2] pinctrl: Allow indicating loss of pin states during low-power

On Fri, Nov 3, 2017 at 12:15 AM, Florian Fainelli wrote: > Some platforms (e.g: Broadcom STB: BMIPS_GENERIC/ARCH_BRCMSTB) will lose > their register contents when entering their lower power state. In such a > case, the pinctrl-single driver that is used will not be able to restore > the power

[PATCH v2 2/2] pinctrl: Allow indicating loss of pin states during low-power

Some platforms (e.g: Broadcom STB: BMIPS_GENERIC/ARCH_BRCMSTB) will lose their register contents when entering their lower power state. In such a case, the pinctrl-single driver that is used will not be able to restore the power states without telling the core about it and having

[PATCH v2 2/2] pinctrl: Allow indicating loss of pin states during low-power

Some platforms (e.g: Broadcom STB: BMIPS_GENERIC/ARCH_BRCMSTB) will lose their register contents when entering their lower power state. In such a case, the pinctrl-single driver that is used will not be able to restore the power states without telling the core about it and having