summaryrefslogtreecommitdiffstats
path: root/drivers/base
diff options
context:
space:
mode:
authorRafael J. Wysocki <rjw@sisk.pl>2011-04-29 00:36:21 +0200
committerRafael J. Wysocki <rjw@sisk.pl>2011-04-29 00:36:21 +0200
commit38ade3a1fa0421c12627c7b48c33e89414fc9b76 (patch)
tree8efd13e1b6368690c31e30b59e130a0559e05eb6 /drivers/base
parent69c9dd1ecf446ad8a830e4afc539a2a1adc85b78 (diff)
downloadop-kernel-dev-38ade3a1fa0421c12627c7b48c33e89414fc9b76.zip
op-kernel-dev-38ade3a1fa0421c12627c7b48c33e89414fc9b76.tar.gz
shmobile: Use power domains for platform runtime PM
shmobile platforms replace the runtime PM callbacks of the platform bus type with their own routines, but this means that the callbacks are replaced system-wide. This may not be the right approach if the platform devices on the system are not of the same type (e.g. some of them belong to an SoC and the others are located in separate chips), because in those cases they may require different handling. Thus it is better to use power domains to override the platform bus type's PM handling, as it generally is possible to use different power domains for devices with different PM requirements. Define a default power domain for shmobile in both the SH and ARM falvors and use it to override the platform bus type's PM callbacks. Since the suspend and hibernate callbacks of the new "default" power domains need to be the same and the platform bus type's suspend and hibernate callbacks for the time being, export those callbacks so that can be used outside of the platform bus type code. Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Diffstat (limited to 'drivers/base')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud