From: Ulf Hansson <ulf.hansson@linaro.org>
To: "Fu, Zhonghui" <zhonghui.fu@linux.intel.com>,
Adrian Hunter <adrian.hunter@intel.com>
Cc: Venu Byravarasu <vbyravarasu@nvidia.com>,
Chaotian Jing <chaotian.jing@mediatek.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Sudeep Holla <Sudeep.Holla@arm.com>,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
linux-mmc <linux-mmc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2 v2] mmc: enable mmc host device to suspend/resume asynchronously
Date: Fri, 29 Jan 2016 12:40:22 +0100 [thread overview]
Message-ID: <CAPDyKFqRGAVuWSbWFEGiDoj8ZUDgpbKty=pNDxiatn4MRKhMYw@mail.gmail.com> (raw)
In-Reply-To: <56A6D6C1.9060805@linux.intel.com>
On 26 January 2016 at 03:15, Fu, Zhonghui <zhonghui.fu@linux.intel.com> wrote:
>
>
> On 1/22/2016 10:51 PM, Ulf Hansson wrote:
>> On 22 January 2016 at 04:32, Fu, Zhonghui <zhonghui.fu@linux.intel.com> wrote:
>>> This patch enables mmc hosts to suspend/resume asynchronously.
>>> This will improve system suspend/resume speed. After applying
>>> this patch and enabling all mmc hosts' child devices to
>>> suspend/resume asynchronously on ASUS T100TA, the system
>>> suspend-to-idle time is reduced from 1645ms to 1107ms, and the
>>> system resume time is reduced from 940ms to 914ms.
>> Do you really reduce time at all with this patch by its own? I think not.
>>
>> Moreover, I thought the biggest improvement came from the patch which
>> enabled async suspend/resume for the MMC/SD/SDIO device?
>> ec076cd226c3 ("mmc: enable MMC/SD/SDIO device to suspend/resume asynchronously")
>>
>> Similar comment applies to patch2/2, but I would expect it together
>> with the $subject patch gives an improvement.
>>
>> Please update the change-logs one more round.
>
> The reduce time is not contributed by only this patch, please see the change-log: "After applying this patch and enabling all mmc hosts' child devices to suspend/resume asynchronously on ASUS T100TA .......". Actually, the biggest improvement came from the patch - "net/wireless: enable wiphy device to suspend/resume asynchronously(commit 9f0e13546ef5773b7059b531a667ec47a5f897ee)". Wiphy device(phy0) is child device of WiFi card(SDIO card).
>
> Do you mean that I should list the reduce time contributed by only this patch and patch2/2 in change-log?
Okay, fair enough. I should have read the change log a bit more detailed.
Let's keep this as is! I have applied both patch 1 and patch2.
Adrian, please tell me if you don't like patch2 (sdhci-acpi), then I
will drop it.
Thanks and kind regards
Uffe
prev parent reply other threads:[~2016-01-29 11:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 3:32 [PATCH 1/2 v2] mmc: enable mmc host device to suspend/resume asynchronously Fu, Zhonghui
2016-01-22 14:51 ` Ulf Hansson
2016-01-26 2:15 ` Fu, Zhonghui
2016-01-29 11:40 ` Ulf Hansson [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='CAPDyKFqRGAVuWSbWFEGiDoj8ZUDgpbKty=pNDxiatn4MRKhMYw@mail.gmail.com' \
--to=ulf.hansson@linaro.org \
--cc=Sudeep.Holla@arm.com \
--cc=adrian.hunter@intel.com \
--cc=chaotian.jing@mediatek.com \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=vbyravarasu@nvidia.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).