Re: Lack of suspend/resume/shutdown ordering between GPIO providers and consumers

On Mon, May 14, 2018 at 04:46:41PM -0700, Florian Fainelli wrote: > On 04/25/2018 11:14 AM, Dmitry Torokhov wrote: > > On Wed, Apr 25, 2018 at 10:00:31AM -0500, Rob Herring wrote: > >> On Tue, Apr 24, 2018 at 5:58 PM, Florian Fainelli > >> wrote: > >>> Hi Linus, Rafael, all

Re: Lack of suspend/resume/shutdown ordering between GPIO providers and consumers

On Mon, May 14, 2018 at 04:46:41PM -0700, Florian Fainelli wrote: > On 04/25/2018 11:14 AM, Dmitry Torokhov wrote: > > On Wed, Apr 25, 2018 at 10:00:31AM -0500, Rob Herring wrote: > >> On Tue, Apr 24, 2018 at 5:58 PM, Florian Fainelli > >> wrote: > >>> Hi Linus, Rafael, all > >>> > >>> Our GPIO

Re: Lack of suspend/resume/shutdown ordering between GPIO providers and consumers

On 04/25/2018 11:14 AM, Dmitry Torokhov wrote: > On Wed, Apr 25, 2018 at 10:00:31AM -0500, Rob Herring wrote: >> On Tue, Apr 24, 2018 at 5:58 PM, Florian Fainelli >> wrote: >>> Hi Linus, Rafael, all >>> >>> Our GPIO controller driver: gpio-brcmstb.c has a shutdown callback

Re: Lack of suspend/resume/shutdown ordering between GPIO providers and consumers

On 04/25/2018 11:14 AM, Dmitry Torokhov wrote: > On Wed, Apr 25, 2018 at 10:00:31AM -0500, Rob Herring wrote: >> On Tue, Apr 24, 2018 at 5:58 PM, Florian Fainelli >> wrote: >>> Hi Linus, Rafael, all >>> >>> Our GPIO controller driver: gpio-brcmstb.c has a shutdown callback which >>> gets invoked

Re: Lack of suspend/resume/shutdown ordering between GPIO providers and consumers

On Wednesday, April 25, 2018 9:29:59 PM CEST Grygorii Strashko wrote: > > On 04/25/2018 02:10 PM, Grygorii Strashko wrote: > > > > > > On 04/25/2018 01:57 PM, Florian Fainelli wrote: > >> On 04/25/2018 11:47 AM, Grygorii Strashko wrote: > >>> > >>> > >>> On 04/25/2018 01:29 PM, Florian Fainelli

Re: Lack of suspend/resume/shutdown ordering between GPIO providers and consumers

On Wednesday, April 25, 2018 9:29:59 PM CEST Grygorii Strashko wrote: > > On 04/25/2018 02:10 PM, Grygorii Strashko wrote: > > > > > > On 04/25/2018 01:57 PM, Florian Fainelli wrote: > >> On 04/25/2018 11:47 AM, Grygorii Strashko wrote: > >>> > >>> > >>> On 04/25/2018 01:29 PM, Florian Fainelli

Re: Lack of suspend/resume/shutdown ordering between GPIO providers and consumers

On Wednesday, April 25, 2018 8:14:35 PM CEST Dmitry Torokhov wrote: > On Wed, Apr 25, 2018 at 10:00:31AM -0500, Rob Herring wrote: > > On Tue, Apr 24, 2018 at 5:58 PM, Florian Fainelli > > wrote: > > > Hi Linus, Rafael, all > > > > > > Our GPIO controller driver:

Re: Lack of suspend/resume/shutdown ordering between GPIO providers and consumers

On Wednesday, April 25, 2018 8:14:35 PM CEST Dmitry Torokhov wrote: > On Wed, Apr 25, 2018 at 10:00:31AM -0500, Rob Herring wrote: > > On Tue, Apr 24, 2018 at 5:58 PM, Florian Fainelli > > wrote: > > > Hi Linus, Rafael, all > > > > > > Our GPIO controller driver: gpio-brcmstb.c has a shutdown

Re: Lack of suspend/resume/shutdown ordering between GPIO providers and consumers

On 04/25/2018 02:10 PM, Grygorii Strashko wrote: On 04/25/2018 01:57 PM, Florian Fainelli wrote: On 04/25/2018 11:47 AM, Grygorii Strashko wrote: On 04/25/2018 01:29 PM, Florian Fainelli wrote: On 04/25/2018 11:06 AM, Grygorii Strashko wrote: On 04/24/2018 05:58 PM, Florian Fainelli

Re: Lack of suspend/resume/shutdown ordering between GPIO providers and consumers

On 04/25/2018 02:10 PM, Grygorii Strashko wrote: On 04/25/2018 01:57 PM, Florian Fainelli wrote: On 04/25/2018 11:47 AM, Grygorii Strashko wrote: On 04/25/2018 01:29 PM, Florian Fainelli wrote: On 04/25/2018 11:06 AM, Grygorii Strashko wrote: On 04/24/2018 05:58 PM, Florian Fainelli

Re: Lack of suspend/resume/shutdown ordering between GPIO providers and consumers

On 04/25/2018 01:57 PM, Florian Fainelli wrote: > On 04/25/2018 11:47 AM, Grygorii Strashko wrote: >> >> >> On 04/25/2018 01:29 PM, Florian Fainelli wrote: >>> On 04/25/2018 11:06 AM, Grygorii Strashko wrote: On 04/24/2018 05:58 PM, Florian Fainelli wrote: > Hi Linus, Rafael,

Re: Lack of suspend/resume/shutdown ordering between GPIO providers and consumers

On 04/25/2018 01:57 PM, Florian Fainelli wrote: > On 04/25/2018 11:47 AM, Grygorii Strashko wrote: >> >> >> On 04/25/2018 01:29 PM, Florian Fainelli wrote: >>> On 04/25/2018 11:06 AM, Grygorii Strashko wrote: On 04/24/2018 05:58 PM, Florian Fainelli wrote: > Hi Linus, Rafael,

Re: Lack of suspend/resume/shutdown ordering between GPIO providers and consumers

On 04/25/2018 11:47 AM, Grygorii Strashko wrote: > > > On 04/25/2018 01:29 PM, Florian Fainelli wrote: >> On 04/25/2018 11:06 AM, Grygorii Strashko wrote: >>> >>> >>> On 04/24/2018 05:58 PM, Florian Fainelli wrote: Hi Linus, Rafael, all Our GPIO controller driver: gpio-brcmstb.c

Re: Lack of suspend/resume/shutdown ordering between GPIO providers and consumers

On 04/25/2018 11:47 AM, Grygorii Strashko wrote: > > > On 04/25/2018 01:29 PM, Florian Fainelli wrote: >> On 04/25/2018 11:06 AM, Grygorii Strashko wrote: >>> >>> >>> On 04/24/2018 05:58 PM, Florian Fainelli wrote: Hi Linus, Rafael, all Our GPIO controller driver: gpio-brcmstb.c

Re: Lack of suspend/resume/shutdown ordering between GPIO providers and consumers

On 04/25/2018 01:29 PM, Florian Fainelli wrote: On 04/25/2018 11:06 AM, Grygorii Strashko wrote: On 04/24/2018 05:58 PM, Florian Fainelli wrote: Hi Linus, Rafael, all Our GPIO controller driver: gpio-brcmstb.c has a shutdown callback which gets invoked when the system is brought into

Re: Lack of suspend/resume/shutdown ordering between GPIO providers and consumers

On 04/25/2018 01:29 PM, Florian Fainelli wrote: On 04/25/2018 11:06 AM, Grygorii Strashko wrote: On 04/24/2018 05:58 PM, Florian Fainelli wrote: Hi Linus, Rafael, all Our GPIO controller driver: gpio-brcmstb.c has a shutdown callback which gets invoked when the system is brought into

Re: Lack of suspend/resume/shutdown ordering between GPIO providers and consumers

On 04/25/2018 11:06 AM, Grygorii Strashko wrote: > > > On 04/24/2018 05:58 PM, Florian Fainelli wrote: >> Hi Linus, Rafael, all >> >> Our GPIO controller driver: gpio-brcmstb.c has a shutdown callback which >> gets invoked when the system is brought into poweroff aka S5. So far so >> good,

Re: Lack of suspend/resume/shutdown ordering between GPIO providers and consumers

On 04/25/2018 11:06 AM, Grygorii Strashko wrote: > > > On 04/24/2018 05:58 PM, Florian Fainelli wrote: >> Hi Linus, Rafael, all >> >> Our GPIO controller driver: gpio-brcmstb.c has a shutdown callback which >> gets invoked when the system is brought into poweroff aka S5. So far so >> good,

Re: Lack of suspend/resume/shutdown ordering between GPIO providers and consumers

On Wed, Apr 25, 2018 at 10:00:31AM -0500, Rob Herring wrote: > On Tue, Apr 24, 2018 at 5:58 PM, Florian Fainelli > wrote: > > Hi Linus, Rafael, all > > > > Our GPIO controller driver: gpio-brcmstb.c has a shutdown callback which > > gets invoked when the system is brought

Re: Lack of suspend/resume/shutdown ordering between GPIO providers and consumers

On Wed, Apr 25, 2018 at 10:00:31AM -0500, Rob Herring wrote: > On Tue, Apr 24, 2018 at 5:58 PM, Florian Fainelli > wrote: > > Hi Linus, Rafael, all > > > > Our GPIO controller driver: gpio-brcmstb.c has a shutdown callback which > > gets invoked when the system is brought into poweroff aka S5.

Re: Lack of suspend/resume/shutdown ordering between GPIO providers and consumers

On 04/24/2018 05:58 PM, Florian Fainelli wrote: Hi Linus, Rafael, all Our GPIO controller driver: gpio-brcmstb.c has a shutdown callback which gets invoked when the system is brought into poweroff aka S5. So far so good, except that we also wish to use gpio_keys.c as a possible wake-up

Re: Lack of suspend/resume/shutdown ordering between GPIO providers and consumers

On 04/24/2018 05:58 PM, Florian Fainelli wrote: Hi Linus, Rafael, all Our GPIO controller driver: gpio-brcmstb.c has a shutdown callback which gets invoked when the system is brought into poweroff aka S5. So far so good, except that we also wish to use gpio_keys.c as a possible wake-up

Re: Lack of suspend/resume/shutdown ordering between GPIO providers and consumers

On Tue, Apr 24, 2018 at 5:58 PM, Florian Fainelli wrote: > Hi Linus, Rafael, all > > Our GPIO controller driver: gpio-brcmstb.c has a shutdown callback which > gets invoked when the system is brought into poweroff aka S5. So far so > good, except that we also wish to use

Re: Lack of suspend/resume/shutdown ordering between GPIO providers and consumers

On Tue, Apr 24, 2018 at 5:58 PM, Florian Fainelli wrote: > Hi Linus, Rafael, all > > Our GPIO controller driver: gpio-brcmstb.c has a shutdown callback which > gets invoked when the system is brought into poweroff aka S5. So far so > good, except that we also wish to use gpio_keys.c as a possible

Lack of suspend/resume/shutdown ordering between GPIO providers and consumers

Hi Linus, Rafael, all Our GPIO controller driver: gpio-brcmstb.c has a shutdown callback which gets invoked when the system is brought into poweroff aka S5. So far so good, except that we also wish to use gpio_keys.c as a possible wake-up source, so we may have a number of GPIO pins declared as

Lack of suspend/resume/shutdown ordering between GPIO providers and consumers

Hi Linus, Rafael, all Our GPIO controller driver: gpio-brcmstb.c has a shutdown callback which gets invoked when the system is brought into poweroff aka S5. So far so good, except that we also wish to use gpio_keys.c as a possible wake-up source, so we may have a number of GPIO pins declared as