On pią, 2014-11-14 at 14:31 +0100, Ulf Hansson wrote:
> On 14 November 2014 09:50, Krzysztof Kozlowski <k.kozlowski@xxxxxxxxxxx> wrote:
> > Add system suspend/resume capabilities to the pl330 driver so the amba
> > bus clock could be also unprepared to conserve energy.
> >
> > Signed-off-by: Krzysztof Kozlowski <k.kozlowski@xxxxxxxxxxx>
> > ---
> > drivers/dma/pl330.c | 41 +++++++++++++++++++++++++++++++++++++++++
> > 1 file changed, 41 insertions(+)
> >
> > diff --git a/drivers/dma/pl330.c b/drivers/dma/pl330.c
> > index c3bd3584f261..e499bb118f0a 100644
> > --- a/drivers/dma/pl330.c
> > +++ b/drivers/dma/pl330.c
> > @@ -2627,6 +2627,46 @@ static int pl330_dma_device_slave_caps(struct dma_chan *dchan,
> > return 0;
> > }
> >
> > +/*
> > + * Runtime PM callbacks are provided by amba/bus.c driver.
> > + *
> > + * It is assumed here that IRQ safe runtime PM is chosen in probe and amba
> > + * bus driver will only disable/enable the clock in runtime PM callbacks.
> > + */
> > +static int __maybe_unused pl330_suspend(struct device *dev)
> > +{
> > + struct amba_device *pcdev = to_amba_device(dev);
> > +
> > + pm_runtime_disable(dev);
> > +
> > + if (!pm_runtime_status_suspended(dev)) {
> > + /* amba did not disable the clock */
> > + amba_pclk_disable(pcdev);
> > + }
> > + amba_pclk_unprepare(pcdev);
>
> I would also invoke pm_runtime_set_suspended() here, to reflect that's
> the current runtime PM state of the device.
Strictly speaking the device is not runtime suspended in that moment. PM
runtime callbacks were not called. Although the device status looks like
runtime suspended (clocks disabled) but I think the whole goal here was
to avoid touching runtime PM because this is system sleep.
> I guess I sounds like broken record :-), but using
> pm_runtime_force_suspend() would help to prevent some code duplication
> here.
>
> Something like this:
>
> pm_runtime_force_suspend()
> if (pm_runtime_is_irq_safe())
> amba_pclk_unprepare(pcdev);
With !CONFIG_PM_RUNTIME this would leave clocks prepared...
Thanks for feedback!
Best regards,
Krzysztof
--
To unsubscribe from this list: send the line "unsubscribe dmaengine" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
