From: Andi Kleen <andi@firstfloor.org>
To: Zhang Rui <rui.zhang@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-pm <linux-pm@lists.linux-foundation.org>,
linux-acpi <linux-acpi@vger.kernel.org>,
Len Brown <lenb@kernel.org>, Pavel Machek <pavel@suse.cz>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
"Van De Ven, Arjan" <arjan.van.de.ven@intel.com>
Subject: Re: [PATCH 0/8] device async action mechanism
Date: Wed, 15 Jul 2009 12:41:33 +0200 [thread overview]
Message-ID: <87ocrm6xeq.fsf@basil.nowhere.org> (raw)
In-Reply-To: <1247643512.26272.74.camel@rzhang-dt> (Zhang Rui's message of "Wed, 15 Jul 2009 15:38:32 +0800")
Zhang Rui <rui.zhang@intel.com> writes:
>
> Currently, in order to make sure that it won't bring any side effects,
> I only convert the ACPI battery and i8042 to use this framework, which reduces
> 0.5s+ S3 time(suspend time plus resume time), from 7.0s to less than 6.5s.
10.5s+ was intended I guess?
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <andi@firstfloor.org>
To: Zhang Rui <rui.zhang@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-pm <linux-pm@lists.linux-foundation.org>,
linux-acpi <linux-acpi@vger.kernel.org>,
Len Brown <lenb@kernel.org>, Pavel Machek <pavel@suse.cz>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
"Van De Ven, Arjan" <arjan.van.de.ven@intel.com>
Subject: Re: [PATCH 0/8] device async action mechanism
Date: Wed, 15 Jul 2009 12:41:33 +0200 [thread overview]
Message-ID: <87ocrm6xeq.fsf@basil.nowhere.org> (raw)
In-Reply-To: <1247643512.26272.74.camel@rzhang-dt> (Zhang Rui's message of "Wed, 15 Jul 2009 15:38:32 +0800")
Zhang Rui <rui.zhang@intel.com> writes:
>
> Currently, in order to make sure that it won't bring any side effects,
> I only convert the ACPI battery and i8042 to use this framework, which reduces
> 0.5s+ S3 time(suspend time plus resume time), from 7.0s to less than 6.5s.
10.5s+ was intended I guess?
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-07-15 10:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 7:38 [PATCH 0/8] device async action mechanism Zhang Rui
2009-07-15 0:29 ` Pavel Machek
2009-07-15 0:29 ` Pavel Machek
2009-07-17 1:40 ` Zhang Rui
2009-07-17 1:40 ` Zhang Rui
2009-07-15 10:41 ` Andi Kleen
2009-07-15 10:41 ` Andi Kleen [this message]
2009-07-15 10:41 ` Andi Kleen
2009-07-16 2:14 ` Zhang Rui
2009-07-16 8:07 ` Andi Kleen
2009-07-16 8:07 ` Andi Kleen
2009-07-16 8:07 ` Andi Kleen
2009-07-16 8:30 ` Zhang Rui
2009-07-16 8:30 ` Zhang Rui
2009-07-16 8:30 ` Zhang Rui
2009-07-16 11:40 ` Henrique de Moraes Holschuh
2009-07-16 13:45 ` Arjan van de Ven
2009-07-16 14:36 ` Fabio Comolli
2009-07-16 14:36 ` Fabio Comolli
2009-07-16 14:36 ` Fabio Comolli
2009-07-17 1:37 ` Zhang Rui
2009-07-17 1:37 ` Zhang Rui
2009-07-16 13:45 ` Arjan van de Ven
2009-07-16 11:40 ` Henrique de Moraes Holschuh
-- strict thread matches above, loose matches on Subject: below --
2009-07-15 7:38 Zhang Rui
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=87ocrm6xeq.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=arjan.van.de.ven@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=pavel@suse.cz \
--cc=rjw@sisk.pl \
--cc=rui.zhang@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.