From: "Fu, Zhonghui" <zhonghui.fu@linux.intel.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] hid: enable hid device to suspend/resume asynchronously
Date: Mon, 23 Nov 2015 14:03:33 +0800 [thread overview]
Message-ID: <5652AC35.5030302@linux.intel.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1511161624360.20111@pobox.suse.cz>
On 11/16/2015 11:26 PM, Jiri Kosina wrote:
> On Mon, 16 Nov 2015, Fu, Zhonghui wrote:
>
>> Hi Jiri,
>>
>> Any comments about this patch?
>>
>> After enabling the HID devices suspend/resume asynchronously on ASUS
>> T100TA(Baytrail-T platform), the system suspend-to-idle/resume time is
>> reduced about 20ms. Although this improvement is not very significant.
>> But, if the suspend/resume operation of HID devices is very
>> time-consuming on some other platforms, this patch can improve
>> significantly system suspend/resume speed on these platforms.
> Hi,
>
> I don't think the question I've raised at
>
> http://lkml.kernel.org/r/alpine.LNX.2.00.1509251404130.30132@pobox.suse.cz
>
> has ever been answered or at least discussed ... ?
Sorry for missing this mail.
At present, the file(/sys/.../power/async) can be used to enable one device suspend/resume asynchronously. My patch only changes the default value of this file from "disabled" to "enabled".
The sole difference of asynchronous suspend/resume mode is that the suspend/resume operation of one device is carried out in a separate kernel thread, and PM core ensures all related dependency. I have verified this patch on some platforms, such as ASUS T100TA. Actually, many other devices have used this feature for a long time.
Thanks,
Zhonghui
>
next prev parent reply other threads:[~2015-11-23 6:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 6:06 [PATCH v2] hid: enable hid device to suspend/resume asynchronously Fu, Zhonghui
2015-11-16 15:17 ` Fu, Zhonghui
2015-11-16 15:26 ` Jiri Kosina
2015-11-23 6:03 ` Fu, Zhonghui [this message]
2015-12-03 8:53 ` Jiri Kosina
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=5652AC35.5030302@linux.intel.com \
--to=zhonghui.fu@linux.intel.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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