Re: [PATCH] ARM: OMAP2+: omap_device: drop broken RPM status update from suspend_noirq

* Johan Hovold [170726 01:36]: > On Wed, Jul 26, 2017 at 01:17:17AM -0700, Tony Lindgren wrote: > * Johan > Hovold [170726 00:51]: > > > On Tue, Jul 25, 2017 at 12:48:40PM -0500, Grygorii Strashko wrote: > > > > So, thank you for your patches and sorry for

Re: [PATCH] ARM: OMAP2+: omap_device: drop broken RPM status update from suspend_noirq

* Johan Hovold [170726 01:36]: > On Wed, Jul 26, 2017 at 01:17:17AM -0700, Tony Lindgren wrote: > * Johan > Hovold [170726 00:51]: > > > On Tue, Jul 25, 2017 at 12:48:40PM -0500, Grygorii Strashko wrote: > > > > So, thank you for your patches and sorry for the noise. > > > > > > > > Tested-by:

Re: [PATCH] ARM: OMAP2+: omap_device: drop broken RPM status update from suspend_noirq

On Wed, Jul 26, 2017 at 01:17:17AM -0700, Tony Lindgren wrote: > * Johan Hovold [170726 00:51]: > > On Tue, Jul 25, 2017 at 12:48:40PM -0500, Grygorii Strashko wrote: > > > So, thank you for your patches and sorry for the noise. > > > > > > Tested-by: Grygorii Strashko

Re: [PATCH] ARM: OMAP2+: omap_device: drop broken RPM status update from suspend_noirq

On Wed, Jul 26, 2017 at 01:17:17AM -0700, Tony Lindgren wrote: > * Johan Hovold [170726 00:51]: > > On Tue, Jul 25, 2017 at 12:48:40PM -0500, Grygorii Strashko wrote: > > > So, thank you for your patches and sorry for the noise. > > > > > > Tested-by: Grygorii Strashko > > > > Thanks for

Re: [PATCH] ARM: OMAP2+: omap_device: drop broken RPM status update from suspend_noirq

* Johan Hovold [170726 00:51]: > On Tue, Jul 25, 2017 at 12:48:40PM -0500, Grygorii Strashko wrote: > > So, thank you for your patches and sorry for the noise. > > > > Tested-by: Grygorii Strashko > > Thanks for testing. So does the patch

Re: [PATCH] ARM: OMAP2+: omap_device: drop broken RPM status update from suspend_noirq

* Johan Hovold [170726 00:51]: > On Tue, Jul 25, 2017 at 12:48:40PM -0500, Grygorii Strashko wrote: > > So, thank you for your patches and sorry for the noise. > > > > Tested-by: Grygorii Strashko > > Thanks for testing. So does the patch description need updating? And this is needed as a fix

Re: [PATCH] ARM: OMAP2+: omap_device: drop broken RPM status update from suspend_noirq

On Tue, Jul 25, 2017 at 12:48:40PM -0500, Grygorii Strashko wrote: > Hi Johan, > > On 07/25/2017 03:24 AM, Johan Hovold wrote: > > On Mon, Jul 24, 2017 at 05:16:02PM -0500, Grygorii Strashko wrote: > >> On 07/24/2017 04:52 AM, Johan Hovold wrote: > >>> Since commit a8636c89648a ("PM / Runtime:

Re: [PATCH] ARM: OMAP2+: omap_device: drop broken RPM status update from suspend_noirq

On Tue, Jul 25, 2017 at 12:48:40PM -0500, Grygorii Strashko wrote: > Hi Johan, > > On 07/25/2017 03:24 AM, Johan Hovold wrote: > > On Mon, Jul 24, 2017 at 05:16:02PM -0500, Grygorii Strashko wrote: > >> On 07/24/2017 04:52 AM, Johan Hovold wrote: > >>> Since commit a8636c89648a ("PM / Runtime:

Re: [PATCH] ARM: OMAP2+: omap_device: drop broken RPM status update from suspend_noirq

Hi Johan, On 07/25/2017 03:24 AM, Johan Hovold wrote: > On Mon, Jul 24, 2017 at 05:16:02PM -0500, Grygorii Strashko wrote: >> On 07/24/2017 04:52 AM, Johan Hovold wrote: >>> Since commit a8636c89648a ("PM / Runtime: Don't allow to suspend a >>> device with an active child"), which went into 4.10,

Re: [PATCH] ARM: OMAP2+: omap_device: drop broken RPM status update from suspend_noirq

Hi Johan, On 07/25/2017 03:24 AM, Johan Hovold wrote: > On Mon, Jul 24, 2017 at 05:16:02PM -0500, Grygorii Strashko wrote: >> On 07/24/2017 04:52 AM, Johan Hovold wrote: >>> Since commit a8636c89648a ("PM / Runtime: Don't allow to suspend a >>> device with an active child"), which went into 4.10,

Re: [PATCH] ARM: OMAP2+: omap_device: drop broken RPM status update from suspend_noirq

On 07/25/2017 03:56 AM, Tony Lindgren wrote: * Tony Lindgren [170725 00:11]: * Grygorii Strashko [170724 15:17]: My personal thought here is that removing of pm_runtime_set_active() will not fix root cause of the problem, but rather hide it :(

Re: [PATCH] ARM: OMAP2+: omap_device: drop broken RPM status update from suspend_noirq

On 07/25/2017 03:56 AM, Tony Lindgren wrote: * Tony Lindgren [170725 00:11]: * Grygorii Strashko [170724 15:17]: My personal thought here is that removing of pm_runtime_set_active() will not fix root cause of the problem, but rather hide it :( and, probably, real fix will be to update USB

Re: [PATCH] ARM: OMAP2+: omap_device: drop broken RPM status update from suspend_noirq

* Tony Lindgren [170725 00:11]: > * Grygorii Strashko [170724 15:17]: > > My personal thought here is that removing of pm_runtime_set_active() will > > not fix > > root cause of the problem, but rather hide it :( and, probably, real fix > > will be

Re: [PATCH] ARM: OMAP2+: omap_device: drop broken RPM status update from suspend_noirq

* Tony Lindgren [170725 00:11]: > * Grygorii Strashko [170724 15:17]: > > My personal thought here is that removing of pm_runtime_set_active() will > > not fix > > root cause of the problem, but rather hide it :( and, probably, real fix > > will be > > to update USB framework to ensure that

Re: [PATCH] ARM: OMAP2+: omap_device: drop broken RPM status update from suspend_noirq

* Johan Hovold [170724 02:53]: > Since commit a8636c89648a ("PM / Runtime: Don't allow to suspend a > device with an active child"), which went into 4.10, it is no longer > permitted to set RPM_SUSPENDED state for a device with active children > (unless power.ignore_children is

Re: [PATCH] ARM: OMAP2+: omap_device: drop broken RPM status update from suspend_noirq

* Johan Hovold [170724 02:53]: > Since commit a8636c89648a ("PM / Runtime: Don't allow to suspend a > device with an active child"), which went into 4.10, it is no longer > permitted to set RPM_SUSPENDED state for a device with active children > (unless power.ignore_children is set). > > This

Re: [PATCH] ARM: OMAP2+: omap_device: drop broken RPM status update from suspend_noirq

On Mon, Jul 24, 2017 at 05:16:02PM -0500, Grygorii Strashko wrote: > On 07/24/2017 04:52 AM, Johan Hovold wrote: > > Since commit a8636c89648a ("PM / Runtime: Don't allow to suspend a > > device with an active child"), which went into 4.10, it is no longer > > permitted to set RPM_SUSPENDED state

Re: [PATCH] ARM: OMAP2+: omap_device: drop broken RPM status update from suspend_noirq

On Mon, Jul 24, 2017 at 05:16:02PM -0500, Grygorii Strashko wrote: > On 07/24/2017 04:52 AM, Johan Hovold wrote: > > Since commit a8636c89648a ("PM / Runtime: Don't allow to suspend a > > device with an active child"), which went into 4.10, it is no longer > > permitted to set RPM_SUSPENDED state

Re: [PATCH] ARM: OMAP2+: omap_device: drop broken RPM status update from suspend_noirq

* Grygorii Strashko [170724 15:17]: > My personal thought here is that removing of pm_runtime_set_active() will not > fix > root cause of the problem, but rather hide it :( and, probably, real fix will > be > to update USB framework to ensure that all suspend devices

Re: [PATCH] ARM: OMAP2+: omap_device: drop broken RPM status update from suspend_noirq

* Grygorii Strashko [170724 15:17]: > My personal thought here is that removing of pm_runtime_set_active() will not > fix > root cause of the problem, but rather hide it :( and, probably, real fix will > be > to update USB framework to ensure that all suspend devices are also PM > runtime

Re: [PATCH] ARM: OMAP2+: omap_device: drop broken RPM status update from suspend_noirq

On 07/24/2017 04:52 AM, Johan Hovold wrote: > Since commit a8636c89648a ("PM / Runtime: Don't allow to suspend a > device with an active child"), which went into 4.10, it is no longer > permitted to set RPM_SUSPENDED state for a device with active children > (unless power.ignore_children is

Re: [PATCH] ARM: OMAP2+: omap_device: drop broken RPM status update from suspend_noirq

On 07/24/2017 04:52 AM, Johan Hovold wrote: > Since commit a8636c89648a ("PM / Runtime: Don't allow to suspend a > device with an active child"), which went into 4.10, it is no longer > permitted to set RPM_SUSPENDED state for a device with active children > (unless power.ignore_children is

[PATCH] ARM: OMAP2+: omap_device: drop broken RPM status update from suspend_noirq

Since commit a8636c89648a ("PM / Runtime: Don't allow to suspend a device with an active child"), which went into 4.10, it is no longer permitted to set RPM_SUSPENDED state for a device with active children (unless power.ignore_children is set). This specifically means that the attempts to do

[PATCH] ARM: OMAP2+: omap_device: drop broken RPM status update from suspend_noirq

Since commit a8636c89648a ("PM / Runtime: Don't allow to suspend a device with an active child"), which went into 4.10, it is no longer permitted to set RPM_SUSPENDED state for a device with active children (unless power.ignore_children is set). This specifically means that the attempts to do