[RFC][PATCH 0/6] PM: Suspend/resume for clock sources/clock event devices in PM domains

[Rafael J. Wysocki]

Hi all,

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.

Thanks,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/