* Mark Brown [off-list ref] [160211 07:54]:

On Thu, Feb 11, 2016 at 07:08:06AM -0800, Tony Lindgren wrote:

quoted

* Mark Brown [off-list ref] [160211 03:52]:

quoted

quoted

Why, I'm not seeing any dependencies here?  I'd also expect to be seeing
an awful lot more changes like this, this shouldn't be an OMAP thing -
do we need to fix the core API and then roll out the transition in a
different way?

quoted

Please feel free to pick up this one if you have other fixes
lined up, nothing stopping that.

I'll take it myself unless there is a strong reason to merge it as part
of another series.

OK thanks!

quoted

There will be likely more fixes like this to make drivers follow
the PM runtime API documentation. These were just the initial
ones that were obvious.

This does sound like there's been a change in the interface compared to
what users are actually doing - is this an actual problem or is it just
a divergence from docs?

It's an actual problem at least on omaps as the omap_device code
is very picky about the hardware state.

Depending how the PM runtime is implemented, it may be a problem
for some other cases too.

For non-omap cases, my guess is that it's mostly a divergence from
the docs and non-critical.

Regards,

Tony