Linux MultiMedia Card development
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-sh@vger.kernel.org, linux-mmc@vger.kernel.org,
	Magnus Damm <damm@opensource.se>,
	Simon Horman <horms@verge.net.au>
Subject: Re: [PATCH v4] mmc: add runtime and system power-management support to the MMCIF driver
Date: Fri, 6 May 2011 19:59:38 +0200	[thread overview]
Message-ID: <201105061959.38964.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.64.1105060955120.10445@axis700.grange>

On Friday, May 06, 2011, Guennadi Liakhovetski wrote:
> On Thu, 5 May 2011, Rafael J. Wysocki wrote:
> 
> > On Thursday, May 05, 2011, Guennadi Liakhovetski wrote:
> > > Adding support for runtime power-management to the MMCIF driver allows
> > > it to save power as long as no card is present. To also allow to turn
> > > off the power domain at that time, we release DMA channels during that
> > > time, since on some sh-mobile systems the DMA controller(s) and the
> > > MMCIF block belong to the same power domain. System-wide power
> > > management has been tested with experimental PM patches on AP4-based
> > > systems.
> > > 
> > > Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
> > > ---
> > > 
> > > This patch supersedes:
> > > 
> > > [PATCH 2/3 v3] MMC: add runtime and system power-management support to the MMCIF driver
> > > 
> > > and has been tested to work with Rafael's suspend git-tree, power-domains 
> > > branch.
> > > 
> > >  drivers/mmc/host/sh_mmcif.c |   78 ++++++++++++++++++++++++++++++++++++++-----
> > >  1 files changed, 69 insertions(+), 9 deletions(-)
> > > 
> > > diff --git a/drivers/mmc/host/sh_mmcif.c b/drivers/mmc/host/sh_mmcif.c
> > > index d3871b6..14f8edb 100644
> > > --- a/drivers/mmc/host/sh_mmcif.c
> > > +++ b/drivers/mmc/host/sh_mmcif.c
> 
> [snip]
> 
> > > @@ -1112,15 +1135,52 @@ static int __devexit sh_mmcif_remove(struct platform_device *pdev)
> > >  
> > >  	clk_disable(host->hclk);
> > >  	mmc_free_host(host->mmc);
> > > +	pm_runtime_put_sync(&pdev->dev);
> > > +	pm_runtime_disable(&pdev->dev);
> > >  
> > >  	return 0;
> > >  }
> > >  
> > > +#ifdef CONFIG_PM
> > > +static int sh_mmcif_suspend(struct device *dev)
> > > +{
> > > +	struct platform_device *pdev = to_platform_device(dev);
> > > +	struct sh_mmcif_host *host = platform_get_drvdata(pdev);
> > > +	int ret = mmc_suspend_host(host->mmc);
> > > +
> > > +	if (!ret) {
> > > +		sh_mmcif_writel(host->addr, MMCIF_CE_INT_MASK, MASK_ALL);
> > > +		clk_disable(host->hclk);
> > > +	}
> > > +
> > > +	return ret;
> > > +}
> > > +
> > > +static int sh_mmcif_resume(struct device *dev)
> > > +{
> > > +	struct platform_device *pdev = to_platform_device(dev);
> > > +	struct sh_mmcif_host *host = platform_get_drvdata(pdev);
> > > +
> > > +	clk_enable(host->hclk);
> > > +
> > > +	return mmc_resume_host(host->mmc);
> > > +}
> > > +#else
> > > +#define sh_mmcif_suspend	NULL
> > > +#define sh_mmcif_resume		NULL
> > > +#endif	/* CONFIG_PM */
> > > +
> > > +static const struct dev_pm_ops sh_mmcif_dev_pm_ops = {
> > > +	.suspend = sh_mmcif_suspend,
> > > +	.resume = sh_mmcif_resume,
> > > +};
> > 
> > So this means the driver only has system-wide suspend/resume callbacks.
> > I guess hibernation is not supported by the target platform(s) yet, so
> > the freeze/thaw etc. callbacks are not necessary at the moment, but in case
> > they are supposed to be the same as the suspend/resume ones, it wouldn't
> > hurt to use SET_SYSTEM_SLEEP_PM_OPS (as defined in include/linux/pm.h).
> 
> Hm, I've tested this with experimental STR patches from Magnus. He has 
> also sent some patches for that to the ML a week ago. So, not sure I need 
> SET_SYSTEM_SLEEP_PM_OPS.

You may not need it right now, but it comes basically without a cost and
the benefit is that people will know what the hibernate callbacks are
supposed to be (in case somebody attempts to implement hibernation on your
target platform(s)).

> > Also, runtime PM callbacks are not present.  Is it intentional?  I thought
> > they would be necessary to save/restore the device state over the power
> > domain power down/power up, wouldn't they?
> 
> This is intentional. We only allow runtime suspend with no cards plugged 
> in, and then there isn't much to save and restore there, on each new card 
> insertion a complete initialisation is taking place anyway.

OK then.

Thanks,
Rafael

      reply	other threads:[~2011-05-06 17:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-05 16:20 [PATCH v4] mmc: add runtime and system power-management support to the MMCIF driver Guennadi Liakhovetski
2011-05-05 21:50 ` Rafael J. Wysocki
2011-05-06  9:06   ` Guennadi Liakhovetski
2011-05-06 17:59     ` Rafael J. Wysocki [this message]

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=201105061959.38964.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=damm@opensource.se \
    --cc=g.liakhovetski@gmx.de \
    --cc=horms@verge.net.au \
    --cc=linux-mmc@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