linux-stable.git/include/drm/intel/display_parent_interface.h, branch v7.3-rc2

drm/{i915, xe}/panic: drop dependency on struct intel_framebuffer

2026-06-23T08:33:07+00:00

Store tiling function pointer in struct intel_panic instead of struct
intel_framebuffer, and store struct intel_panic pointer instead of
struct intel_framebuffer pointer in struct drm_scanout_buffer private
member.

To make this happen, pass the tiling function pointer to panic setup
hook, and initialize sb->private in the hook for clarity.

This allows us to drop the dependency on struct intel_framebuffer from
i915 and xe panic code.

Note: It would be less verbose to have a typedef for the tiling function
pointer. However, there isn't a nice location for it that wouldn't also
increase header interdependencies.

Cc: Jocelyn Falempe 
Reviewed-by: Jocelyn Falempe 
Link: https://patch.msgid.link/d97abae79db3437c617cd4cb6193ba017b3a8d78.1780394867.git.jani.nikula@intel.com
Signed-off-by: Jani Nikula

drm/{i915,xe}/panic: pass obj to panic setup

2026-06-23T08:33:07+00:00

Start reducing i915 and xe core dependency on struct intel_framebuffer
by passing the fb obj from display.

Cc: Jocelyn Falempe 
Reviewed-by: Jocelyn Falempe 
Link: https://patch.msgid.link/840c4ccaced5f1c82277285938287776c8cdf513.1780394867.git.jani.nikula@intel.com
Signed-off-by: Jani Nikula

drm/i915: Introduce the main fb_pin parent interface

2026-05-11T14:43:25+00:00

Introduce the main part of the new fb_pin parent interface:
- intel_parent_fb_pin_ggtt_(un)pin()
- intel_parent_fb_pin_dpt_(un)pin()
- intel_parent_fb_pin_reuse_vma()

Reviewed-by: Jani Nikula 
Signed-off-by: Ville Syrjälä 
Link: https://patch.msgid.link/20260508143426.26504-14-ville.syrjala@linux.intel.com

drm/i915: Move intel_fb_pin_params to the parent interface

2026-05-11T14:43:24+00:00

strut intel_fb_pin_params will be an important part of the fb_pin
interface, so move the definition to the parent interface file.

Or maybe we should have a separate header for this kind of stuff
since the users of the parent interface will need the struct
definition but not the parent interface vfunc struct definitions?

Reviewed-by: Jani Nikula 
Signed-off-by: Ville Syrjälä 
Link: https://patch.msgid.link/20260508143426.26504-3-ville.syrjala@linux.intel.com

drm/i915: Introduce intel_parent_fb_pin_get_map()

2026-05-11T14:43:24+00:00

Introduce the "fb_pin" parent interface, as the first trivial step
move the *_get_map() stuff there.

The whole "fb_pin" as an interface might not really make sense,
and perhaps this (and other stuff) should just be collected into
some kind of "bo" interface. But let's go with "fb_pin" for now
to match where things are implemented, and possibly restructure
it later.

Reviewed-by: Jani Nikula 
Signed-off-by: Ville Syrjälä 
Link: https://patch.msgid.link/20260508143426.26504-2-ville.syrjala@linux.intel.com

drm/i915: Remove the vma parent interface

2026-04-15T17:36:24+00:00

With the fb pinning stuff directly returning the fence_id
there is no longer any need for the vma parent interface.
Get rid of it.

Reviewed-by: Jani Nikula 
Signed-off-by: Ville Syrjälä 
Link: https://patch.msgid.link/20260407170942.16515-2-ville.syrjala@linux.intel.com

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

2026-04-15T09:37:51+00:00

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ä 
Link: https://patch.msgid.link/20260410150449.9699-6-ville.syrjala@linux.intel.com
Reviewed-by: Jani Nikula

drm/i915: Introduce sanity to the plane_config pointer vs. array thing

2026-04-15T09:35:25+00:00

The "plane_config" vs. "plane_configs" naming difference is very
subtle, making it far too easy to use the wrong thing by accident.
Introduce a separate type for the array, making it impossible to
pass in the wrong thing. And while at it name the variable
"all_plane_configs" to help the poor reader make sense of things.

The .config_fini() prototype also mistakenly used the plural
form despite only taking in a singular plane_config. So fix that
one up as well.

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

drm/{i915, xe}: move fbdev fb calls to parent interface

2026-04-02T07:45:59+00:00

Move the driver specific fbdev fb calls to the display parent
interface. Reuse the existing struct intel_display_bo_interface, as this
is mostly about gem objects.

Put everything behind IS_ENABLED(CONFIG_DRM_FBDEV_EMULATION) to catch
configuration issues at build or link time.

v2: Rebase

Reviewed-by: Michał Grzelak  # v1
Link: https://patch.msgid.link/a6bb24909a58181cfc41b91a4c6538a181d27158.1774950508.git.jani.nikula@intel.com
Signed-off-by: Jani Nikula

drm/i915: move VLV IOSF sideband to display parent interface

2026-04-01T09:29:17+00:00

Remove another direct dependency from display to i915 core by moving the
VLV IOSF sideband calls to the display parent interface. Xe doesn't need
this, so it'll remain optional and NULL.

Reviewed-by: Ville Syrjälä 
Link: https://patch.msgid.link/15dfc67b58f5b5b381be0f9bc66d60b43bebfecf.1774957233.git.jani.nikula@intel.com
Signed-off-by: Jani Nikula