On Wed, Dec 04, 2013 at 03:28:25PM +0100, Jonas Gorski wrote:
> On Wed, Dec 4, 2013 at 3:08 PM, Mark Brown <broonie@xxxxxxxxxx> wrote:
> > You'll need to call pm_runtime_enable() and so on to turn on runtime PM
> > in probe() and reverse that in remove() but otherwise no, just adding
> > the runtime callbacks should be fine.
> I see. Looks like I just copied your oversight from
> 5355d96d6fb56507761f261a23c0831f67fa0e0f ("spi/bcm63xx: Convert to
> core runtime PM") :P I'll add that to my list of things to fix.
The driver was already broken there - the requirement to enable runtime
PM is a part of the core runtime PM API. All that change did was factor
out the enable and disable calls.
> Grepping through drivers/spi, I see a few drivers not calling
> pm_runtime_enable(), but setting auto_runtime_pm to true, and a few
> doing the opposite. These should probably aligned, too.
Not using the core runtime PM is fine, there may be reasons the driver
wants to do this by hand. Things not enabling runtime PM are definitely
buggy though.
Attachment:
signature.asc
Description: Digital signature
