On Monday, October 30, 2017 11:19:08 AM CET Rafael J. Wysocki wrote:
> On Mon, Oct 30, 2017 at 8:10 AM, Tero Kristo <t-kri...@ti.com> wrote:
> > The recent change to the PM QoS framework to introduce a proper
> > no constraint value overlooked to handle the devices which don't
> > implement PM QoS OPS. Runtime PM is one of the more severely
> > impacted subsystems, failing every attempt to runtime suspend
> > a device. This leads into some nasty second level issues like
> > probe failures and increased power consumption among other things.
>
> Oh, that's bad.
>
> Sorry about breaking it and thanks for the fix!
>
> > Fix this by adding a proper return value for devices that don't
> > implement PM QoS implicitly.
> >
> > Fixes: 0cc2b4e5a020 ("PM / QoS: Fix device resume latency PM QoS")
> > Signed-off-by: Tero Kristo <t-kri...@ti.com>
> > Cc: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
>
> Applied.
And pushed to Linus.
That said, probe shouldn't ever fail if PM QoS is set to the
"never suspend" value.
User space can set it that way, after all, so the drivers that fail to probe
in that case aren't correct I'm afraid.
Thanks,
Rafael
