diff options
author | Rafael J. Wysocki <rjw@sisk.pl> | 2011-11-17 21:39:33 +0100 |
---|---|---|
committer | Rafael J. Wysocki <rjw@sisk.pl> | 2011-11-17 21:39:33 +0100 |
commit | 8b258cc8ac229aa7d5dcb7cc34cb35d9124498ac (patch) | |
tree | 9615636b05b04035af0c8eb11ee9711aa2b868a6 /arch/arm/mach-shmobile/pm-sh7372.c | |
parent | af8db1508f2c9f3b6e633e2d2d906c6557c617f9 (diff) | |
download | blackbird-op-linux-8b258cc8ac229aa7d5dcb7cc34cb35d9124498ac.tar.gz blackbird-op-linux-8b258cc8ac229aa7d5dcb7cc34cb35d9124498ac.zip |
PM Sleep: Do not extend wakeup paths to devices with ignore_children set
Commit 4ca46ff3e0d8c234cb40ebb6457653b59584426c (PM / Sleep: Mark
devices involved in wakeup signaling during suspend) introduced
the power.wakeup_path field in struct dev_pm_info to mark devices
whose children are enabled to wake up the system from sleep states,
so that power domains containing the parents that provide their
children with wakeup power and/or relay their wakeup signals are not
turned off. Unfortunately, that introduced a PM regression on SH7372
whose power consumption in the system "memory sleep" state increased
as a result of it, because it prevented the power domain containing
the I2C controller from being turned off when some children of that
controller were enabled to wake up the system, although the
controller was not necessary for them to signal wakeup.
To fix this issue use the observation that devices whose
power.ignore_children flag is set for runtime PM should be treated
analogously during system suspend. Namely, they shouldn't be
included in wakeup paths going through their children. Since the
SH7372 I2C controller's power.ignore_children flag is set, doing so
will restore the previous behavior of that SOC.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'arch/arm/mach-shmobile/pm-sh7372.c')
0 files changed, 0 insertions, 0 deletions