Re: [PATCH v10 1/5] PM / Runtime: Allow accessing irq_safe if no PM_RUNTIME

2014-11-10 Thread Ulf Hansson
On 10 November 2014 17:36, Alan Stern wrote: > On Mon, 10 Nov 2014, Ulf Hansson wrote: > >> > To me, this sounds like a good reason to avoid using >> > force_runtime_suspend(). In fact, it sounds like a good reason to >> > avoid relying on the runtime PM mechanism to handle non-runtime-PM >> >

Re: [PATCH v10 1/5] PM / Runtime: Allow accessing irq_safe if no PM_RUNTIME

2014-11-10 Thread Alan Stern
On Mon, 10 Nov 2014, Ulf Hansson wrote: > > To me, this sounds like a good reason to avoid using > > force_runtime_suspend(). In fact, it sounds like a good reason to > > avoid relying on the runtime PM mechanism to handle non-runtime-PM > > things (like a system suspend callback). If

Re: [PATCH v10 1/5] PM / Runtime: Allow accessing irq_safe if no PM_RUNTIME

2014-11-10 Thread Ulf Hansson
On 7 November 2014 15:50, Alan Stern wrote: > On Fri, 7 Nov 2014, Krzysztof Kozlowski wrote: > >> > Well, that is a good reason to introduce a wrapper around power.irq_safe >> > in my >> > view. >> > >> > And define the wrapper so that it always returns false for >> > CONFIG_PM_RUNTIME >> >

Re: [PATCH v10 1/5] PM / Runtime: Allow accessing irq_safe if no PM_RUNTIME

2014-11-10 Thread Srikanth K
unsubscribe -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Re: [PATCH v10 1/5] PM / Runtime: Allow accessing irq_safe if no PM_RUNTIME

2014-11-10 Thread Ulf Hansson
On 7 November 2014 09:06, Krzysztof Kozlowski wrote: > On czw, 2014-11-06 at 23:51 +0100, Rafael J. Wysocki wrote: >> On Thursday, November 06, 2014 09:36:46 AM Krzysztof Kozlowski wrote: >> > Some drivers (e.g. bus drivers) may want to check if power.irq_safe was >> > called by child driver,

Re: [PATCH v10 1/5] PM / Runtime: Allow accessing irq_safe if no PM_RUNTIME

2014-11-10 Thread Ulf Hansson
On 7 November 2014 09:06, Krzysztof Kozlowski k.kozlow...@samsung.com wrote: On czw, 2014-11-06 at 23:51 +0100, Rafael J. Wysocki wrote: On Thursday, November 06, 2014 09:36:46 AM Krzysztof Kozlowski wrote: Some drivers (e.g. bus drivers) may want to check if power.irq_safe was called by

Re: [PATCH v10 1/5] PM / Runtime: Allow accessing irq_safe if no PM_RUNTIME

2014-11-10 Thread Srikanth K
unsubscribe -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Re: [PATCH v10 1/5] PM / Runtime: Allow accessing irq_safe if no PM_RUNTIME

2014-11-10 Thread Ulf Hansson
On 7 November 2014 15:50, Alan Stern st...@rowland.harvard.edu wrote: On Fri, 7 Nov 2014, Krzysztof Kozlowski wrote: Well, that is a good reason to introduce a wrapper around power.irq_safe in my view. And define the wrapper so that it always returns false for CONFIG_PM_RUNTIME

Re: [PATCH v10 1/5] PM / Runtime: Allow accessing irq_safe if no PM_RUNTIME

2014-11-10 Thread Alan Stern
On Mon, 10 Nov 2014, Ulf Hansson wrote: To me, this sounds like a good reason to avoid using force_runtime_suspend(). In fact, it sounds like a good reason to avoid relying on the runtime PM mechanism to handle non-runtime-PM things (like a system suspend callback). If CONFIG_PM_RUNTIME

Re: [PATCH v10 1/5] PM / Runtime: Allow accessing irq_safe if no PM_RUNTIME

2014-11-10 Thread Ulf Hansson
On 10 November 2014 17:36, Alan Stern st...@rowland.harvard.edu wrote: On Mon, 10 Nov 2014, Ulf Hansson wrote: To me, this sounds like a good reason to avoid using force_runtime_suspend(). In fact, it sounds like a good reason to avoid relying on the runtime PM mechanism to handle

Re: [PATCH v10 1/5] PM / Runtime: Allow accessing irq_safe if no PM_RUNTIME

2014-11-07 Thread Rafael J. Wysocki
On Friday, November 07, 2014 09:50:58 AM Alan Stern wrote: > On Fri, 7 Nov 2014, Krzysztof Kozlowski wrote: > > > > Well, that is a good reason to introduce a wrapper around power.irq_safe > > > in my > > > view. > > > > > > And define the wrapper so that it always returns false for > > >

Re: [PATCH v10 1/5] PM / Runtime: Allow accessing irq_safe if no PM_RUNTIME

2014-11-07 Thread Alan Stern
On Fri, 7 Nov 2014, Krzysztof Kozlowski wrote: > > Well, that is a good reason to introduce a wrapper around power.irq_safe in > > my > > view. > > > > And define the wrapper so that it always returns false for CONFIG_PM_RUNTIME > > unset. > > > > This way not only you wouldn't need to move

Re: [PATCH v10 1/5] PM / Runtime: Allow accessing irq_safe if no PM_RUNTIME

2014-11-07 Thread Krzysztof Kozlowski
On czw, 2014-11-06 at 23:51 +0100, Rafael J. Wysocki wrote: > On Thursday, November 06, 2014 09:36:46 AM Krzysztof Kozlowski wrote: > > Some drivers (e.g. bus drivers) may want to check if power.irq_safe was > > called by child driver, regardless of CONFIG_PM_RUNTIME. > > > > An example scenario

Re: [PATCH v10 1/5] PM / Runtime: Allow accessing irq_safe if no PM_RUNTIME

2014-11-07 Thread Krzysztof Kozlowski
On czw, 2014-11-06 at 23:51 +0100, Rafael J. Wysocki wrote: On Thursday, November 06, 2014 09:36:46 AM Krzysztof Kozlowski wrote: Some drivers (e.g. bus drivers) may want to check if power.irq_safe was called by child driver, regardless of CONFIG_PM_RUNTIME. An example scenario is

Re: [PATCH v10 1/5] PM / Runtime: Allow accessing irq_safe if no PM_RUNTIME

2014-11-07 Thread Alan Stern
On Fri, 7 Nov 2014, Krzysztof Kozlowski wrote: Well, that is a good reason to introduce a wrapper around power.irq_safe in my view. And define the wrapper so that it always returns false for CONFIG_PM_RUNTIME unset. This way not only you wouldn't need to move the flag from

Re: [PATCH v10 1/5] PM / Runtime: Allow accessing irq_safe if no PM_RUNTIME

2014-11-07 Thread Rafael J. Wysocki
On Friday, November 07, 2014 09:50:58 AM Alan Stern wrote: On Fri, 7 Nov 2014, Krzysztof Kozlowski wrote: Well, that is a good reason to introduce a wrapper around power.irq_safe in my view. And define the wrapper so that it always returns false for CONFIG_PM_RUNTIME

Re: [PATCH v10 1/5] PM / Runtime: Allow accessing irq_safe if no PM_RUNTIME

2014-11-06 Thread Rafael J. Wysocki
On Thursday, November 06, 2014 09:36:46 AM Krzysztof Kozlowski wrote: > Some drivers (e.g. bus drivers) may want to check if power.irq_safe was > called by child driver, regardless of CONFIG_PM_RUNTIME. > > An example scenario is amba/bus.c and dma/pl330.c drivers. The runtime > suspend/resume

Re: [PATCH v10 1/5] PM / Runtime: Allow accessing irq_safe if no PM_RUNTIME

2014-11-06 Thread Ulf Hansson
On 6 November 2014 09:36, Krzysztof Kozlowski wrote: > Some drivers (e.g. bus drivers) may want to check if power.irq_safe was > called by child driver, regardless of CONFIG_PM_RUNTIME. > > An example scenario is amba/bus.c and dma/pl330.c drivers. The runtime > suspend/resume callbacks in amba

[PATCH v10 1/5] PM / Runtime: Allow accessing irq_safe if no PM_RUNTIME

2014-11-06 Thread Krzysztof Kozlowski
Some drivers (e.g. bus drivers) may want to check if power.irq_safe was called by child driver, regardless of CONFIG_PM_RUNTIME. An example scenario is amba/bus.c and dma/pl330.c drivers. The runtime suspend/resume callbacks in amba bus driver act differently if irq_safe was set by child driver

Re: [PATCH v10 1/5] PM / Runtime: Allow accessing irq_safe if no PM_RUNTIME

2014-11-06 Thread Rafael J. Wysocki
On Thursday, November 06, 2014 09:36:46 AM Krzysztof Kozlowski wrote: Some drivers (e.g. bus drivers) may want to check if power.irq_safe was called by child driver, regardless of CONFIG_PM_RUNTIME. An example scenario is amba/bus.c and dma/pl330.c drivers. The runtime suspend/resume

[PATCH v10 1/5] PM / Runtime: Allow accessing irq_safe if no PM_RUNTIME

2014-11-06 Thread Krzysztof Kozlowski
Some drivers (e.g. bus drivers) may want to check if power.irq_safe was called by child driver, regardless of CONFIG_PM_RUNTIME. An example scenario is amba/bus.c and dma/pl330.c drivers. The runtime suspend/resume callbacks in amba bus driver act differently if irq_safe was set by child driver

Re: [PATCH v10 1/5] PM / Runtime: Allow accessing irq_safe if no PM_RUNTIME

2014-11-06 Thread Ulf Hansson
On 6 November 2014 09:36, Krzysztof Kozlowski k.kozlow...@samsung.com wrote: Some drivers (e.g. bus drivers) may want to check if power.irq_safe was called by child driver, regardless of CONFIG_PM_RUNTIME. An example scenario is amba/bus.c and dma/pl330.c drivers. The runtime suspend/resume