|From:||"Rafael J. Wysocki" <email@example.com>|
|To:||Linux PM list <firstname.lastname@example.org>|
|Subject:||[PATCH 0/15] PM: Suspend/resume and runtime PM for clock sources/clock event devices in PM domains|
|Date:||Mon, 6 Aug 2012 01:38:03 +0200|
|Cc:||LKML <email@example.com>, "Linux-sh list" <firstname.lastname@example.org>, Magnus Damm <email@example.com>, Paul Mundt <firstname.lastname@example.org>, Thomas Gleixner <email@example.com>|
Hi all, On Sunday, July 29, 2012, Rafael J. Wysocki wrote: > There is a problem with clock sources and clock event devices belonging to PM > domains that they have to be marked as "always on", to prevent those domains > from being turned off unexpectedly, which also prevents the domains from > being turned off during system suspend, although that might be done and would > be desirable. > > The following patch series introduces a mechanism by which the generic PM > domains framework can be notified that a given domain may be turned off > after timekeeping has been suspended, which allows the domains that contain > clock sources and clock event devices to be turned off before the system > enters the target sleep state (so that less power is used in that state). > > [1/6] Introduce simplified power on routine for PM domains (to be used during > system resume from suspend/hibernation and during "syscore" resume). > [2/6] Introduce function for notifying the generic PM domains framework that > the given device may be treated as suspended (so its domain may be > turned off if this has been the last active device in it). > [3/6] Introduce suspend/resume callbacks for clock event devices. > [4/6] Make the SH TMU driver use suspend/resume callbacks for clock sources > and clock event devices to notify the generic PM domains framework that > those devices may be regarded as suspended (during system suspend) or > that they have to be turned on immediately (during system resume). > [5/6] Like [4/6] but for the SH CMT driver. > [6/6] Analogous to [4/6], but for the SH MTU2 driver. > > The patchset has been tested on the SH7372 Mackerel board. There were no comments, so I think I can go a bit further and add runtime PM support to those drivers too. :-) This requires some core changes, but they aren't too invasive in my opinion. Patches [1-6/15] are more-or-less the same as before modulo some fixes for bugs found during more thorough testing. The remaining patches make the following changes: [7/15] - Clean up device PM initialization. [8/15] - Allow early platform device drivers to use runtime PM helper functions. [9/15] - Rename the "always_on" device flag to "syscore". [10/15] - Move the "syscore" flag to the core (from PM domains framework). [11/15] - Rework the "starting" of devices flagged as "irq safe" in PM domains. [12/15] - Add runtime PM support to the SH TMU driver. [13/15] - Add runtime PM support to the SH CMT driver. [14/15] - Add runtime PM support to the SH MTU2 driver. [15/15] - Stop using the "syscore" device flag for runtime PM. Thanks, Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Copyright © 2012, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds