diff options
| author | Ulf Hansson <[email protected]> | 2016-10-13 14:58:54 +0000 |
|---|---|---|
| committer | Rafael J. Wysocki <[email protected]> | 2016-11-18 23:15:39 +0000 |
| commit | 1d9174fbc55ec99ccbfcafa3de2528ef78a849aa (patch) | |
| tree | 7554f95445c5a71a76fd4a044e8a595b94471e89 /drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | |
| parent | PM / Runtime: Don't allow to suspend a device with an active child (diff) | |
| download | kernel-1d9174fbc55ec99ccbfcafa3de2528ef78a849aa.tar.gz kernel-1d9174fbc55ec99ccbfcafa3de2528ef78a849aa.zip | |
PM / Runtime: Defer resuming of the device in pm_runtime_force_resume()
When the pm_runtime_force_suspend|resume() helpers were invented, we still
had CONFIG_PM_RUNTIME and CONFIG_PM_SLEEP as separate Kconfig options.
To make sure these helpers worked for all combinations and without
introducing too much of complexity, the device was always resumed in
pm_runtime_force_resume().
More precisely, when CONFIG_PM_SLEEP was set and CONFIG_PM_RUNTIME was
unset, we needed to resume the device as the subsystem/driver couldn't
rely on using runtime PM to do it.
As the CONFIG_PM_RUNTIME option was merged into CONFIG_PM a while ago, it
removed this combination, of using CONFIG_PM_SLEEP without the earlier
CONFIG_PM_RUNTIME.
For this reason we can now rely on the subsystem/driver to use runtime PM
to resume the device, instead of forcing that to be done in all cases. In
other words, let's defer the runtime resume to a later point when it's
actually needed.
Signed-off-by: Ulf Hansson <[email protected]>
Tested-by: Marek Szyprowski <[email protected]>
Tested-by: Geert Uytterhoeven <[email protected]>
Acked-by: Kevin Hilman <[email protected]>
Signed-off-by: Rafael J. Wysocki <[email protected]>
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_object.c')
0 files changed, 0 insertions, 0 deletions
