linux-kernel - Re: [PATCH] MMC/SDIO: enable SDIO device to suspend/resume asynchronously

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 17 Aug 2015 09:48:33 +0300
From:	Adrian Hunter <adrian.hunter@...el.com>
To:	"Fu, Zhonghui" <zhonghui.fu@...ux.intel.com>,
	Ulf Hansson <ulf.hansson@...aro.org>, neilb@...e.de,
	Jaehoon Chung <jh80.chung@...sung.com>, afenkart@...il.com,
	joe@...ches.com
CC:	linux-mmc <linux-mmc@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] MMC/SDIO: enable SDIO device to suspend/resume asynchronously

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@...ux.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
>>
> 
> 
> 

--
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/