[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110803123953.GB23953@n2100.arm.linux.org.uk>
Date: Wed, 3 Aug 2011 13:39:53 +0100
From: Russell King - ARM Linux <linux@....linux.org.uk>
To: Viresh Kumar <viresh.kumar@...com>
Cc: linus.walleij@...aro.org, pratyush.anand@...com,
rajeev-dlh.kumar@...com, bhupesh.sharma@...com,
shiraz.hashim@...com, vinod.koul@...el.com,
linux-kernel@...r.kernel.org, vipin.kumar@...com,
armando.visconti@...com, amit.virdi@...com,
vipulkumar.samar@...com, viresh.linux@...il.com,
deepak.sikri@...com, dan.j.williams@...el.com,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH V2 08/20] dmaengine/amba-pl08x: support runtime PM
On Mon, Aug 01, 2011 at 03:07:18PM +0530, Viresh Kumar wrote:
> Insert notifiers for the runtime PM API. With this the runtime PM layer kicks in
> to action where used. This will also handle enabling/disabling of interface
> clock (Code will be added in amba/bus.c by Russell King).
I don't think this is correct...
> @@ -879,11 +880,19 @@ static void pl08x_free_txd_list(struct pl08x_driver_data *pl08x,
> */
> static int pl08x_alloc_chan_resources(struct dma_chan *chan)
> {
> + struct pl08x_dma_chan *plchan = to_pl08x_chan(chan);
> + struct pl08x_driver_data *pl08x = plchan->host;
> +
> + pm_runtime_resume(&pl08x->adev->dev);
Shouldn't this be pm_runtime_get_sync() ?
> return 0;
> }
>
> static void pl08x_free_chan_resources(struct dma_chan *chan)
> {
> + struct pl08x_dma_chan *plchan = to_pl08x_chan(chan);
> + struct pl08x_driver_data *pl08x = plchan->host;
> +
> + pm_runtime_suspend(&pl08x->adev->dev);
And pm_runtime_put() ?
> }
>
> /*
> @@ -1993,6 +2002,8 @@ static int pl08x_probe(struct amba_device *adev, const struct amba_id *id)
> dev_info(&pl08x->adev->dev, "DMA: PL%03x rev%u at 0x%08llx irq %d\n",
> amba_part(adev), amba_rev(adev),
> (unsigned long long)adev->res.start, adev->irq[0]);
> +
> + pm_runtime_suspend(&adev->dev);
And pm_runtime_put() ?
We don't want to call pm_runtime_suspend/resume directly because that
could have bad consequences if more than one channel is in use.
The enabling and disabling of runtime PM for AMBA devices will be handled
in the core code...
Lastly, we may want to make this even tighter to the actual period that
the DMA is being used, rather than just the period that a driver has
been allocated a channel. I'd rather have it done that way now (and
tested) so that we achieve maximal effect from runtime PM, rather than
having something which needs to be revisited again.
IOW, if this is worth doing, then its worth doing properly first time.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists