From: Kevin Hilman <khilman@ti.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux PM list <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>, Greg KH <gregkh@suse.de>,
Magnus Damm <magnus.damm@gmail.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH 0/3] PM / Sleep: Introduce new phases of device suspend/resume
Date: Mon, 30 Jan 2012 14:37:18 -0800 [thread overview]
Message-ID: <87ehugrf4x.fsf@ti.com> (raw)
In-Reply-To: <201201252336.36179.rjw@sisk.pl> (Rafael J. Wysocki's message of "Wed, 25 Jan 2012 23:36:35 +0100")
"Rafael J. Wysocki" <rjw@sisk.pl> writes:
> On Wednesday, January 25, 2012, Kevin Hilman wrote:
>> "Rafael J. Wysocki" <rjw@sisk.pl> writes:
>>
>> > Hi,
>> >
>> > On Friday, December 23, 2011, Rafael J. Wysocki wrote:
>> >> Hi,
>> >>
>> >> On the request of some driver PM developers, that appears to have been quite
>> >> popular lately, this series of patches adds new system suspend/resume (and
>> >> hibernation/restore) callbacks to struct dev_pm_ops and makes the PM core
>> >> use them during system power transitions.
>> >>
>> >> [1/2] - Introduce "late suspend" and "early resume" of devices.
>> >> [2/2] - Introduce generic callbacks for new device PM phases.
>> >>
>> >> The series is on top of the linux-next branch of the linux-pm tree.
>> >>
>> >> These patches have been tested on Toshiba Portege R500 with openSUSE 12.1
>> >> without crashing the box in the process, which looks promising. Also,
>> >> they shouldn't actually have any impact on the existing setups other than
>> >> adding a very short delay to the system suspend/resume code paths.
>> >
>> > The patches have received some more testing since the were first posted and
>> > I've added a PM domains patch on top of them:
>> >
>> > [3/3] - Make generic PM domains use the new device suspend/resume phases.
>> >
>> > The series applies on top of linux-pm/pm-for-linus (although it should
>> > apply on top of the current mainline too).
>> >
>> > I'm considering these patches as v3.4 material, if there are no objections.
>>
>> Reviewed-by: Kevin Hilman <khilman@ti.com>
>>
>> Thanks Rafael for working on this.
>>
>> So far I've only reviewed it, but I plan to convert my PM domain noirq
>> usage to this and give it some testing as well, hopefully this week.
>
> Great, thanks!
>
OK, I gave it a test on OMAP by converting our _noirq usage to the new
early/late callbacks. Works great. Thanks!
Tested-by: Kevin Hilman <khilman@ti.com>
Kevin
next prev parent reply other threads:[~2012-01-30 22:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 23:29 [RFC][PATCH 0/2] PM / Sleep: Introduce new phases of device suspend/resume Rafael J. Wysocki
2011-12-22 23:30 ` [RFC][PATCH 1/2] PM / Sleep: Introduce "late suspend" and "early resume" of devices Rafael J. Wysocki
2011-12-26 19:14 ` Mark Brown
2011-12-22 23:31 ` [RFC][PATCH 2/2] PM / Sleep: Introduce generic callbacks for new device PM phases Rafael J. Wysocki
2012-01-16 22:21 ` [PATCH 0/3] PM / Sleep: Introduce new phases of device suspend/resume Rafael J. Wysocki
2012-01-16 22:22 ` [PATCH 1/3][Resend] PM / Sleep: Introduce "late suspend" and "early resume" of devices Rafael J. Wysocki
2012-01-16 22:23 ` [PATCH 2/3][Resend] PM / Sleep: Introduce generic callbacks for new device PM phases Rafael J. Wysocki
2012-01-16 22:24 ` [PATCH 3/3] PM / Domains: Run late/early device suspend callbacks at the right time Rafael J. Wysocki
2012-01-16 23:59 ` [PATCH 0/3] PM / Sleep: Introduce new phases of device suspend/resume Greg KH
2012-01-17 22:17 ` Rafael J. Wysocki
2012-01-25 1:07 ` Kevin Hilman
2012-01-25 22:36 ` Rafael J. Wysocki
2012-01-30 22:37 ` Kevin Hilman [this message]
2012-01-30 22:50 ` Rafael J. Wysocki
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=87ehugrf4x.fsf@ti.com \
--to=khilman@ti.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=rjw@sisk.pl \
/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).