All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@intel.com>
To: "Fu, Zhonghui" <zhonghui.fu@linux.intel.com>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	neilb@suse.de, Jaehoon Chung <jh80.chung@samsung.com>,
	afenkart@gmail.com, joe@perches.com
Cc: linux-mmc <linux-mmc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MMC/SDIO: enable SDIO device to suspend/resume asynchronously
Date: Mon, 17 Aug 2015 09:48:33 +0300	[thread overview]
Message-ID: <55D183C1.1030209@intel.com> (raw)
In-Reply-To: <55D1546D.1070900@linux.intel.com>

On 17/08/15 06:26, Fu, Zhonghui wrote:
> 
> Hi,
> 
> Any comments are welcome.
> 
> 
> Thanks,
> Zhonghui
> 
> On 2015/7/30 15:40, Fu, Zhonghui wrote:
>> Enable SDIO card and function device to suspend/resume asynchronously.
>> This can improve system suspend/resume speed.

For me, it needs more explanation.

For example, why is this worth doing?  Can you give an example where it does
significantly improve suspend/resume speed?  Are there any cases where it
could be worse?

Why is it safe?  Presumably it is safe if there are no dependencies on the
device outside the device hierarchy. Is that so?  Are there any other
potential pitfalls to enabling async_suspend?

>>
>> Signed-off-by: Zhonghui Fu <zhonghui.fu@linux.intel.com>
>> ---
>>  drivers/mmc/core/sdio.c |    4 ++++
>>  1 files changed, 4 insertions(+), 0 deletions(-)
>>
>> diff --git a/drivers/mmc/core/sdio.c b/drivers/mmc/core/sdio.c
>> index b91abed..6719b77 100644
>> --- a/drivers/mmc/core/sdio.c
>> +++ b/drivers/mmc/core/sdio.c
>> @@ -1106,6 +1106,8 @@ int mmc_attach_sdio(struct mmc_host *host)
>>  		pm_runtime_enable(&card->dev);
>>  	}
>>  
>> +	device_enable_async_suspend(&card->dev);
>> +
>>  	/*
>>  	 * The number of functions on the card is encoded inside
>>  	 * the ocr.
>> @@ -1126,6 +1128,8 @@ int mmc_attach_sdio(struct mmc_host *host)
>>  		 */
>>  		if (host->caps & MMC_CAP_POWER_OFF_CARD)
>>  			pm_runtime_enable(&card->sdio_func[i]->dev);
>> +
>> +		device_enable_async_suspend(&card->sdio_func[i]->dev);
>>  	}
>>  
>>  	/*
>> -- 1.7.1
>>
> 
> 
> 


  reply	other threads:[~2015-08-17  6:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-30  7:40 [PATCH] MMC/SDIO: enable SDIO device to suspend/resume asynchronously Fu, Zhonghui
2015-08-17  3:26 ` Fu, Zhonghui
2015-08-17  6:48   ` Adrian Hunter [this message]
2015-08-24  7:07     ` Fu, Zhonghui
     [not found]       ` <55FF95CA.4010108@linux.intel.com>
2015-09-21  8:15         ` Adrian Hunter
2015-09-21  8:41           ` Adrian Hunter
2015-11-15 14:02             ` Fu, Zhonghui

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=55D183C1.1030209@intel.com \
    --to=adrian.hunter@intel.com \
    --cc=afenkart@gmail.com \
    --cc=jh80.chung@samsung.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=ulf.hansson@linaro.org \
    --cc=zhonghui.fu@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.