summaryrefslogtreecommitdiff
path: root/drivers/virtio
diff options
context:
space:
mode:
authorJani Nikula <jani.nikula@intel.com>2026-07-01 16:53:02 +0300
committerJani Nikula <jani.nikula@intel.com>2026-07-03 15:35:02 +0300
commit93094e9099e06c1d2b505cc5b9d7bd256bc107a2 (patch)
tree7db585df7edd58284e555a9c34048c6d089c901f /drivers/virtio
parent8d880fe6f6d0b477e1c83460abd8dc09cb4270d3 (diff)
downloadlinux-next-93094e9099e06c1d2b505cc5b9d7bd256bc107a2.tar.gz
linux-next-93094e9099e06c1d2b505cc5b9d7bd256bc107a2.zip
drm/i915: add intel_display_driver_pm_runtime*() functions
Add new functions intel_display_driver_pm_runtime_suspend(), intel_display_driver_pm_runtime_suspend_late(), intel_display_driver_pm_runtime_resume_early(), and intel_display_driver_pm_runtime_resume(). The IRQ suspend/resume is meant to happen between the corresponding calls. For now, intel_display_driver_pm_runtime_suspend() is empty, but is included for completeness as a placeholder. Initially, only migrate i915, as there are some differences with xe that will be addressed later. There's a functional change, which should be benign: i915_pm_runtime_resume() moves intel_opregion_notify_adapter() call slightly later. In the interest of not introducing more severe functional changes, the calls become slightly asymmetric. We might want to address this later. v2: - Rebase, move placement of suspend calls Cc: Rodrigo Vivi <rodrigo.vivi@intel.com> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com> Link: https://patch.msgid.link/81e29bd9bee6c023d079ab076af7dc4b7e8985ca.1782913901.git.jani.nikula@intel.com Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Diffstat (limited to 'drivers/virtio')
0 files changed, 0 insertions, 0 deletions