diff options
| author | Kevin Hilman <khilman@ti.com> | 2012-07-11 02:29:04 +0400 |
|---|---|---|
| committer | Kevin Hilman <khilman@ti.com> | 2012-09-12 21:51:56 +0400 |
| commit | 72bb6f9b51c82c820ddef892455a85b115460904 (patch) | |
| tree | 1b1fd1b1b04e53b3d8ecbef706e69e396f1010a6 /include | |
| parent | e753345bec8fef81d1e87710917f89dc75f39b2a (diff) | |
| download | linux-72bb6f9b51c82c820ddef892455a85b115460904.tar.xz | |
ARM: OMAP: omap_device: don't attempt late suspend if no driver bound
Currently, the omap_device PM domain layer uses the late suspend and
early resume callbacks to ensure devices are in their low power
states.
However, this is attempted even in cases where a driver probe has
failed. If a driver's ->probe() method fails, the driver is likely in
a state where it is not expecting its runtime PM callbacks to be
called, yet currently the omap_device PM domain code attempts to call
the drivers callbacks.
To fix, use the omap_device driver_status field to check whether a
driver is bound to the omap_device before attempting to trigger driver
callbacks.
Reviewed-by: Paul Walmsley <paul@pwsan.com>
Signed-off-by: Kevin Hilman <khilman@ti.com>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions