drm/i915: Move initial plane vblank wait into display code

Browse source

The initial plane vblank wait operates on display registers,
so it really belongs in the display code proper. Move it there.

We can use intel_parent_irq_enabled() to determine if we can
rely on interrupts or not.

On average we should end up waiting half a frame here, so the
polling interval can be fairly long. 1 ms (which actually
makes poll_timeout_us() use ~250-1000 usec) seems good enough
to me.

Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Link: https://patch.msgid.link/20260410150449.9699-6-ville.syrjala@linux.intel.com
Reviewed-by: Jani Nikula <jani.nikula@intel.com>

...

This commit is contained in:

Ville Syrjälä 2026-04-10 18:04:44 +03:00

parent 24104d589d

commit 36f1cddea7

4 changed files with 21 additions and 28 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

22

drivers/gpu/drm/i915/display/intel_initial_plane.c

View file

6

drivers/gpu/drm/i915/i915_initial_plane.c

View file

19

drivers/gpu/drm/xe/display/xe_initial_plane.c

View file

2

include/drm/intel/display_parent_interface.h

View file