summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/bin/stackcollapse-report
diff options
context:
space:
mode:
authorJani Nikula <jani.nikula@intel.com>2026-06-02 11:32:51 +0300
committerJani Nikula <jani.nikula@intel.com>2026-06-04 13:50:09 +0300
commitad317c4de574b356a684954663842263d1acd044 (patch)
treefb6cf24a755c9ff515cb6085b938616044b15137 /tools/perf/scripts/python/bin/stackcollapse-report
parentf7cadbee8aa4768713e57650e7afd8b67e26664d (diff)
drm/xe/display: use intel_display_driver_pm_shutdown()
Replace direct intel_display_driver_pm_suspend() and additional calls with intel_display_driver_shutdown(). This switches to use drm_atomic_helper_shutdown() instead of drm_atomic_helper_suspend(), which is the more appropriate thing to do anyway. Not calling intel_display_driver_pm_suspend() from the xe shutdown path unblocks further follow-up changes. There's a slight functional change in that intel_display_driver_shutdown() returns early for !HAS_DISPLAY(). Assume this is what we want, and there are no cases where display engine is present but all pipes have been fused off. Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com> Link: https://patch.msgid.link/e6783c063f8c0d4a2b413e550165896a3d977585.1780389001.git.jani.nikula@intel.com Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions