diff options
| author |   Gustavo Sousa <gustavo.sousa@intel.com> | 2024-11-29 13:37:55 -0300 |
|---|---|---|
| committer |   Rodrigo Vivi <rodrigo.vivi@intel.com> | 2024-11-30 12:07:30 -0500 |
| commit | a72f1bbf0c3dc06206ae38c6faaf8be5ab6fe168 (patch) | |
| tree | b5f7e4303ff7d987b4e5f393cbb7c475531f75e2 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | drm/i915/dmc_wl: Extract intel_dmc_wl_flush_release_work() (diff) | |
| download | wireguard-linux-a72f1bbf0c3dc06206ae38c6faaf8be5ab6fe168.tar.xz wireguard-linux-a72f1bbf0c3dc06206ae38c6faaf8be5ab6fe168.zip | |
drm/xe/display: Extract xe_display_pm_runtime_suspend_late()
The current behavior for the runtime suspend case is that
xe_display_pm_suspend_late() is only called when D3cold is allowed.
Let's incorporate that behavior into a function specific to runtime PM
and call it xe_display_pm_runtime_suspend_late().
With that, we keep stuff a bit more self-contained and allow having a
place for adding more "late display runtime suspend"-related logic that
isn't dependent on the "D3cold allowed" state.
v2:
- Fix typo in that caused xe_display_pm_runtime_suspend_late() to call
itself instead of xe_display_pm_suspend_late().
- Add the empty version of xe_display_pm_runtime_suspend_late() for
the !CONFIG_DRM_XE_DISPLAY case.
Signed-off-by: Gustavo Sousa <gustavo.sousa@intel.com>
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20241129164010.29887-3-gustavo.sousa@intel.com
Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions