public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@intel.com>
To: Ulf Hansson <ulf.hansson@stericsson.com>
Cc: linux-mmc@vger.kernel.org, Chris Ball <cjb@laptop.org>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Maya Erez <merez@codeaurora.org>,
	Subhash Jadavani <subhashj@codeaurora.org>,
	Arnd Bergmann <arnd@arndb.de>, Kevin Liu <kliu5@marvell.com>,
	Daniel Drake <dsd@laptop.org>, Ohad Ben-Cohen <ohad@wizery.com>
Subject: Re: [PATCH V3 2/4] mmc: core: Add bus_ops for runtime pm callbacks
Date: Mon, 29 Apr 2013 10:54:34 +0300	[thread overview]
Message-ID: <517E273A.8010904@intel.com> (raw)
In-Reply-To: <517A7D19.9020704@intel.com>

On 26/04/13 16:11, Adrian Hunter wrote:
> On 16/04/13 13:00, Ulf Hansson wrote:
>> From: Ulf Hansson <ulf.hansson@linaro.org>
>>
>> SDIO is the only protocol that uses runtime pm for the card device
>> right now. To provide the option for sd and mmc to use runtime pm as
>> well the bus_ops callback are extended with two new functions. One for
>> runtime_suspend and one for runtime_resume.
>>
>> This patch will also implement the callbacks for SDIO to make sure
>> existing functionality is maintained. It also prepares to move
>> away from using the mmc_power_restore_host API, since it is not
>> needed when using runtime PM.
> 
> You have removed the bus_ops checks without explanation.  Are you sure it is
> OK to do so?  I noticed that, in the SDIO case, runtime pm is not disabled
> before detaching the bus making it hard to know if host->bus_ops can
> disappear catastrophically during a runtime pm callback.

Looking at this again - it seems OK.  bus_ops are only detached after
host->bus_ops->remove is called which deletes the device (device_del)
disabling runtime pm.

> 
>>
>> Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
>> Cc: Maya Erez <merez@codeaurora.org>
>> Cc: Subhash Jadavani <subhashj@codeaurora.org>
>> Cc: Arnd Bergmann <arnd@arndb.de>
>> Cc: Kevin Liu <kliu5@marvell.com>
>> Cc: Adrian Hunter <adrian.hunter@intel.com>
>> Cc: Daniel Drake <dsd@laptop.org>
>> Cc: Ohad Ben-Cohen <ohad@wizery.com>
>> ---
>>  drivers/mmc/core/bus.c  |   14 ++++++++++++--
>>  drivers/mmc/core/core.c |    2 +-
>>  drivers/mmc/core/core.h |    3 +++
>>  drivers/mmc/core/sdio.c |   16 ++++++++++++++++
>>  4 files changed, 32 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/mmc/core/bus.c b/drivers/mmc/core/bus.c
>> index e219c97..d9e8c2b 100644
>> --- a/drivers/mmc/core/bus.c
>> +++ b/drivers/mmc/core/bus.c
>> @@ -151,15 +151,25 @@ static int mmc_bus_resume(struct device *dev)
>>  static int mmc_runtime_suspend(struct device *dev)
>>  {
>>  	struct mmc_card *card = mmc_dev_to_card(dev);
>> +	struct mmc_host *host = card->host;
>> +	int ret = 0;
>> +
>> +	if (host->bus_ops->runtime_suspend)
>> +		ret = host->bus_ops->runtime_suspend(host);
>>  
>> -	return mmc_power_save_host(card->host);
>> +	return ret;
>>  }
>>  
>>  static int mmc_runtime_resume(struct device *dev)
>>  {
>>  	struct mmc_card *card = mmc_dev_to_card(dev);
>> +	struct mmc_host *host = card->host;
>> +	int ret = 0;
>> +
>> +	if (host->bus_ops->runtime_resume)
>> +		ret = host->bus_ops->runtime_resume(host);
>>  
>> -	return mmc_power_restore_host(card->host);
>> +	return ret;
>>  }
>>  
>>  static int mmc_runtime_idle(struct device *dev)
>> diff --git a/drivers/mmc/core/core.c b/drivers/mmc/core/core.c
>> index f001097..b16b64a 100644
>> --- a/drivers/mmc/core/core.c
>> +++ b/drivers/mmc/core/core.c
>> @@ -1459,7 +1459,7 @@ void mmc_set_driver_type(struct mmc_host *host, unsigned int drv_type)
>>   * If a host does all the power sequencing itself, ignore the
>>   * initial MMC_POWER_UP stage.
>>   */
>> -static void mmc_power_up(struct mmc_host *host)
>> +void mmc_power_up(struct mmc_host *host)
>>  {
>>  	int bit;
>>  
>> diff --git a/drivers/mmc/core/core.h b/drivers/mmc/core/core.h
>> index b9f18a2..6242ffb 100644
>> --- a/drivers/mmc/core/core.h
>> +++ b/drivers/mmc/core/core.h
>> @@ -22,6 +22,8 @@ struct mmc_bus_ops {
>>  	void (*detect)(struct mmc_host *);
>>  	int (*suspend)(struct mmc_host *);
>>  	int (*resume)(struct mmc_host *);
>> +	int (*runtime_suspend)(struct mmc_host *);
>> +	int (*runtime_resume)(struct mmc_host *);
>>  	int (*power_save)(struct mmc_host *);
>>  	int (*power_restore)(struct mmc_host *);
>>  	int (*alive)(struct mmc_host *);
>> @@ -44,6 +46,7 @@ int mmc_set_signal_voltage(struct mmc_host *host, int signal_voltage);
>>  int __mmc_set_signal_voltage(struct mmc_host *host, int signal_voltage);
>>  void mmc_set_timing(struct mmc_host *host, unsigned int timing);
>>  void mmc_set_driver_type(struct mmc_host *host, unsigned int drv_type);
>> +void mmc_power_up(struct mmc_host *host);
>>  void mmc_power_off(struct mmc_host *host);
>>  void mmc_power_cycle(struct mmc_host *host);
>>  
>> diff --git a/drivers/mmc/core/sdio.c b/drivers/mmc/core/sdio.c
>> index aa0719a..09428c7 100644
>> --- a/drivers/mmc/core/sdio.c
>> +++ b/drivers/mmc/core/sdio.c
>> @@ -1049,11 +1049,27 @@ out:
>>  	return ret;
>>  }
>>  
>> +static int mmc_sdio_runtime_suspend(struct mmc_host *host)
>> +{
>> +	/* No references to the card, cut the power to it. */
>> +	mmc_power_off(host);
>> +	return 0;
>> +}
>> +
>> +static int mmc_sdio_runtime_resume(struct mmc_host *host)
>> +{
>> +	/* Restore power and re-initialize. */
>> +	mmc_power_up(host);
>> +	return mmc_sdio_power_restore(host);
>> +}
>> +
>>  static const struct mmc_bus_ops mmc_sdio_ops = {
>>  	.remove = mmc_sdio_remove,
>>  	.detect = mmc_sdio_detect,
>>  	.suspend = mmc_sdio_suspend,
>>  	.resume = mmc_sdio_resume,
>> +	.runtime_suspend = mmc_sdio_runtime_suspend,
>> +	.runtime_resume = mmc_sdio_runtime_resume,
>>  	.power_restore = mmc_sdio_power_restore,
>>  	.alive = mmc_sdio_alive,
>>  };
>>
> 
> 
> 


  reply	other threads:[~2013-04-29  7:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-16 10:00 [PATCH V3 0/4] mmc: Use runtime pm for blkdevice Ulf Hansson
2013-04-16 10:00 ` [PATCH V3 1/4] mmc: core: Stop bkops for eMMC only from mmc suspend Ulf Hansson
2013-04-18  7:17   ` Jaehoon Chung
2013-04-16 10:00 ` [PATCH V3 2/4] mmc: core: Add bus_ops for runtime pm callbacks Ulf Hansson
2013-04-26 13:11   ` Adrian Hunter
2013-04-29  7:54     ` Adrian Hunter [this message]
2013-04-29 13:42       ` Ulf Hansson
2013-04-16 10:00 ` [PATCH V3 3/4] mmc: block: Enable runtime pm for mmc blkdevice Ulf Hansson
2013-05-02  8:58   ` Adrian Hunter
2013-05-02  9:52     ` Ulf Hansson
2013-05-02  9:57       ` Asutosh Das
2013-05-02 11:09         ` Ulf Hansson
2013-05-02 12:22           ` Adrian Hunter
     [not found]   ` <CAMj5BkiOmh8sz-=b0z1VF9owGPX0KpbZeNfPzETemCb=C2odGQ@mail.gmail.com>
2013-05-24  8:27     ` Ulf Hansson
     [not found]       ` <CAMj5Bki+1=DSzQWYyEC1L=Pa6LpSFQKF3YvoUkkuq62wHuMWow@mail.gmail.com>
2013-05-27  7:51         ` Ulf Hansson
2013-05-27  7:52           ` Ulf Hansson
2013-05-28  6:49             ` zhangfei gao
2013-04-16 10:00 ` [PATCH V3 4/4] mmc: core: Support aggressive power management for (e)MMC/SD Ulf Hansson
2013-05-02 10:38   ` Adrian Hunter
2013-05-02 11:35     ` Ulf Hansson
2013-05-02 12:24       ` Adrian Hunter

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=517E273A.8010904@intel.com \
    --to=adrian.hunter@intel.com \
    --cc=arnd@arndb.de \
    --cc=cjb@laptop.org \
    --cc=dsd@laptop.org \
    --cc=kliu5@marvell.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=merez@codeaurora.org \
    --cc=ohad@wizery.com \
    --cc=subhashj@codeaurora.org \
    --cc=ulf.hansson@linaro.org \
    --cc=ulf.hansson@stericsson.com \
    /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