On Fri, Jan 31, 2014 at 11:47:04PM +0100, Maxime Ripard wrote:
> On Fri, Jan 31, 2014 at 12:48:09PM +0000, Mark Brown wrote:
> > On Fri, Jan 31, 2014 at 11:55:50AM +0100, Maxime Ripard wrote:
> > > + pm_runtime_enable(&pdev->dev);
> > > + if (!pm_runtime_enabled(&pdev->dev)) {
> > > + ret = sun6i_spi_runtime_resume(&pdev->dev);
> > > + if (ret) {
> > > + dev_err(&pdev->dev, "Couldn't resume the device\n");
> > > + return ret;
> > > + }
> > > + }
> > No, as discussed don't do this - notice how other drivers aren't written
> > this way either. Like I said leave the device powered on startup and
> > then let it be idled by runtime PM.
> Well, some SPI drivers are actually written like that (all the tegra
It's not been done consistently, no - that should be fixed.
> SPI drivers for example). It's not an excuse, but waking up the device
> only to put it back in suspend right away seems kind of
It isn't awesome, no. Ideally the runtime PM code would do this but
then you couldn't ifdef the operations which as far as I can tell is the
main thing people want from disabling it and it gets complicated for
devices that genuinely do power up on startup so here we are.
> inefficient. Plus, the pm_runtime_idle callback you suggested are
> actually calling runtime_idle, while we want to call runtime_suspend.
Yeah, I didn't actually check if I was looking at the right call there.
Attachment:
signature.asc
Description: Digital signature
