From: "Koul, Vinod" <vinod.koul@intel.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
Simon Horman <horms@verge.net.au>,
Magnus Damm <damm@opensource.se>
Subject: Re: [PATCH 2/2] dmaengine: shdma: add runtime- and system-level power management
Date: Mon, 02 May 2011 13:33:11 +0530 [thread overview]
Message-ID: <1304323391.1589.9.camel@vkoul-udesk3> (raw)
In-Reply-To: <Pine.LNX.4.64.1104291908090.17813@axis700.grange>
On Fri, 2011-04-29 at 19:09 +0200, Guennadi Liakhovetski wrote:
> This patch extends and fixes runtime power management in the shdma
> driver to support powering down the DMA controller and adds support
> for system-level suspend and resume.
>
> Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
> ---
> drivers/dma/shdma.c | 68 +++++++++++++++++++++++++++++++++++++++++++++++++++
> drivers/dma/shdma.h | 1 +
> 2 files changed, 69 insertions(+), 0 deletions(-)
>
>
> +static int sh_dmae_runtime_suspend(struct device *dev)
> +{
> + return 0;
> +}
Don't you need to initialize you device on resume...????
> +
> +static int sh_dmae_runtime_resume(struct device *dev)
> +{
> + struct sh_dmae_device *shdev = dev_get_drvdata(dev);
> +
> + return sh_dmae_rst(shdev);
> +}
> +
> +#ifdef CONFIG_PM
This should be removed...
> +static int sh_dmae_suspend(struct device *dev)
> +{
> + struct sh_dmae_device *shdev = dev_get_drvdata(dev);
> + int i;
> +
> + for (i = 0; i < shdev->pdata->channel_num; i++) {
> + struct sh_dmae_chan *sh_chan = shdev->chan[i];
> + if (sh_chan->descs_allocated)
> + sh_chan->pm_error = pm_runtime_put_sync(dev);
> + }
> +
> + return 0;
> +}
> +
> +static int sh_dmae_resume(struct device *dev)
> +{
> + struct sh_dmae_device *shdev = dev_get_drvdata(dev);
> + int i;
> +
> + for (i = 0; i < shdev->pdata->channel_num; i++) {
> + struct sh_dmae_chan *sh_chan = shdev->chan[i];
> + struct sh_dmae_slave *param = sh_chan->common.private;
> +
> + if (!sh_chan->descs_allocated)
> + continue;
> +
> + if (!sh_chan->pm_error)
> + pm_runtime_get_sync(dev);
> +
> + if (param) {
> + const struct sh_dmae_slave_config *cfg = param->config;
> + dmae_set_dmars(sh_chan, cfg->mid_rid);
> + dmae_set_chcr(sh_chan, cfg->chcr);
> + } else {
> + dmae_init(sh_chan);
> + }
> + }
> +
> + return 0;
> +}
> +#else
> +#define sh_dmae_suspend NULL
> +#define sh_dmae_resume NULL
> +#endif
> +
> +const struct dev_pm_ops sh_dmae_pm = {
> + .suspend = sh_dmae_suspend,
> + .resume = sh_dmae_resume,
> + .runtime_suspend = sh_dmae_runtime_suspend,
> + .runtime_resume = sh_dmae_runtime_resume,
> +};
> +
> static struct platform_driver sh_dmae_driver = {
> .remove = __exit_p(sh_dmae_remove),
> .shutdown = sh_dmae_shutdown,
> .driver = {
> .owner = THIS_MODULE,
> .name = "sh-dma-engine",
> + .pm = &sh_dmae_pm,
> },
> };
>
> diff --git a/drivers/dma/shdma.h b/drivers/dma/shdma.h
> index 52e4fb1..3f9d3cd 100644
> --- a/drivers/dma/shdma.h
> +++ b/drivers/dma/shdma.h
> @@ -37,6 +37,7 @@ struct sh_dmae_chan {
> int id; /* Raw id of this channel */
> u32 __iomem *base;
> char dev_id[16]; /* unique name per DMAC of channel */
> + int pm_error;
> };
>
> struct sh_dmae_device {
And please remember to CC maintainers...
--
~Vinod
next prev parent reply other threads:[~2011-05-02 8:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 17:09 [PATCH 0/2] locking power management for shdma dmaengine driver Guennadi Liakhovetski
2011-04-29 17:09 ` [PATCH 1/2] dmaengine: shdma: fix locking Guennadi Liakhovetski
2011-05-31 6:50 ` Paul Mundt
2011-05-31 9:26 ` Guennadi Liakhovetski
2011-04-29 17:09 ` [PATCH 2/2] dmaengine: shdma: add runtime- and system-level power management Guennadi Liakhovetski
2011-05-02 8:03 ` Koul, Vinod [this message]
2011-05-02 9:04 ` Guennadi Liakhovetski
2011-05-02 8:38 ` Koul, Vinod
2011-05-02 9:53 ` Guennadi Liakhovetski
2011-05-02 10:05 ` Koul, Vinod
2011-05-02 7:20 ` [PATCH 0/2] locking power management for shdma dmaengine driver Simon Horman
2011-05-02 7:59 ` Guennadi Liakhovetski
2011-05-02 10:51 ` Simon Horman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1304323391.1589.9.camel@vkoul-udesk3 \
--to=vinod.koul@intel.com \
--cc=damm@opensource.se \
--cc=dan.j.williams@intel.com \
--cc=g.liakhovetski@gmx.de \
--cc=horms@verge.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®