diff options
| author | Guangshuo Li <lgs201920130244@gmail.com> | 2026-08-08 21:41:37 +0800 |
|---|---|---|
| committer | Lyude Paul <lyude@redhat.com> | 2026-09-17 18:12:08 -0400 |
| commit | fefd9480ec361969f1a836df46326a1801062c26 (patch) | |
| tree | c9fedcc99be9f5f19117ad42e3196cbfd17e7dd5 /tools/perf/scripts/python/stackcollapse.py | |
| parent | f7eae6d8d768fabd6b59779ca7da79e02c74e113 (diff) | |
| download | linux-next-fefd9480ec361969f1a836df46326a1801062c26.tar.gz linux-next-fefd9480ec361969f1a836df46326a1801062c26.zip | |
drm/nouveau: fix autosuspend cleanup during teardown
nouveau_drm_device_init() calls pm_runtime_use_autosuspend(), but
nouveau_drm_device_fini() does not call the matching
pm_runtime_dont_use_autosuspend().
If the autosuspend delay is set to a negative value while autosuspend
is enabled, the runtime PM core increments usage_count to prevent
runtime suspend. Without calling pm_runtime_dont_use_autosuspend()
during teardown, this reference is not dropped and usage_count remains
unbalanced.
The documentation for pm_runtime_use_autosuspend() also notes that it
is important to undo it with pm_runtime_dont_use_autosuspend() at
driver exit time, unless runtime PM was initially enabled with
devm_pm_runtime_enable().
Add the missing pm_runtime_dont_use_autosuspend() call to the common
device teardown path.
This issue was found by manual code inspection.
Fixes: 5addcf0a5f0f ("nouveau: add runtime PM support (v0.9)")
Cc: stable@vger.kernel.org
Signed-off-by: Guangshuo Li <lgs201920130244@gmail.com>
Reviewed-by: Lyude Paul <lyude@redhat.com>
Signed-off-by: Lyude Paul <lyude@redhat.com>
Link: https://patch.msgid.link/20260808134137.2864847-1-lgs201920130244@gmail.com
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions
