From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 10/16] drm/xe: Introduce xe_fb_pin_dpt_(un)pin()
Date: Fri, 24 Apr 2026 13:12:05 +0300 [thread overview]
Message-ID: <5c693619e1f9551c8cc8ad5cfce521e45216f574@intel.com> (raw)
In-Reply-To: <20260423165346.20884-11-ville.syrjala@linux.intel.com>
On Thu, 23 Apr 2026, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Extract the inner DPT parts of intel_plane_(un)pin() into the
> xe_fb_pin_dpt_(un)pin(). These will become part of the new
> fb_pin parent interface.
>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
> ---
> drivers/gpu/drm/xe/display/xe_fb_pin.c | 69 ++++++++++++++++++++++----
> 1 file changed, 59 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/display/xe_fb_pin.c b/drivers/gpu/drm/xe/display/xe_fb_pin.c
> index 9774089ee75c..46f6ae6acc4e 100644
> --- a/drivers/gpu/drm/xe/display/xe_fb_pin.c
> +++ b/drivers/gpu/drm/xe/display/xe_fb_pin.c
> @@ -428,6 +428,36 @@ void intel_fb_unpin_vma(struct i915_vma *vma, int fence_id)
> __xe_unpin_fb_vma(vma);
> }
>
> +static int xe_fb_pin_dpt_pin(struct drm_gem_object *obj, struct intel_dpt *dpt,
> + const struct intel_fb_pin_params *pin_params,
> + struct i915_vma **out_dpt_vma,
> + struct i915_vma **out_ggtt_vma,
> + u32 *out_offset)
> +{
> + struct i915_vma *ggtt_vma;
> +
> + WARN_ON(dpt);
> +
> + ggtt_vma = __xe_pin_fb_vma(obj, true, pin_params);
> + if (IS_ERR(ggtt_vma))
> + return PTR_ERR(ggtt_vma);
> +
> + *out_dpt_vma = NULL; /* not used on xe */
> + *out_ggtt_vma = ggtt_vma;
> + *out_offset = xe_ggtt_node_addr(ggtt_vma->node);
> +
> + return 0;
> +}
> +
> +static void xe_fb_pin_dpt_unpin(struct intel_dpt *dpt,
> + struct i915_vma *dpt_vma,
> + struct i915_vma *ggtt_vma)
> +{
> + WARN_ON(dpt || dpt_vma);
> +
> + __xe_unpin_fb_vma(ggtt_vma);
> +}
> +
> static bool reuse_vma(struct intel_plane_state *new_plane_state,
> const struct intel_plane_state *old_plane_state)
> {
> @@ -457,27 +487,35 @@ static bool reuse_vma(struct intel_plane_state *new_plane_state,
> int intel_plane_pin_fb(struct intel_plane_state *new_plane_state,
> const struct intel_plane_state *old_plane_state)
> {
> - struct drm_framebuffer *fb = new_plane_state->hw.fb;
> - struct drm_gem_object *obj = intel_fb_bo(fb);
> + struct intel_framebuffer *fb = to_intel_framebuffer(new_plane_state->hw.fb);
> + struct drm_gem_object *obj = intel_fb_bo(&fb->base);
> struct intel_plane *plane = to_intel_plane(new_plane_state->uapi.plane);
> struct intel_fb_pin_params pin_params = {
> .view = &new_plane_state->view.gtt,
> - .alignment = plane->min_alignment(plane, fb, 0),
> - .needs_cpu_lmem_access = intel_fb_needs_cpu_access(fb),
> + .alignment = plane->min_alignment(plane, &fb->base, 0),
> + .needs_cpu_lmem_access = intel_fb_needs_cpu_access(&fb->base),
> };
> struct i915_vma *ggtt_vma = NULL;
> struct i915_vma *dpt_vma = NULL;
> int fence_id = -1;
> u32 offset;
> + int ret;
>
> if (reuse_vma(new_plane_state, old_plane_state))
> return 0;
>
> - ggtt_vma = __xe_pin_fb_vma(obj, intel_fb_uses_dpt(fb), &pin_params);
> - if (IS_ERR(ggtt_vma))
> - return PTR_ERR(ggtt_vma);
> + if (!intel_fb_uses_dpt(&fb->base)) {
> + ggtt_vma = __xe_pin_fb_vma(obj, false, &pin_params);
> + if (IS_ERR(ggtt_vma))
> + return PTR_ERR(ggtt_vma);
>
> - offset = xe_ggtt_node_addr(ggtt_vma->node);
> + offset = xe_ggtt_node_addr(ggtt_vma->node);
> + } else {
> + ret = xe_fb_pin_dpt_pin(obj, fb->dpt, &pin_params,
> + &dpt_vma, &ggtt_vma, &offset);
> + if (ret)
> + return ret;
> + }
>
> new_plane_state->dpt_vma = dpt_vma;
> new_plane_state->ggtt_vma = ggtt_vma;
> @@ -489,8 +527,19 @@ int intel_plane_pin_fb(struct intel_plane_state *new_plane_state,
>
> void intel_plane_unpin_fb(struct intel_plane_state *old_plane_state)
> {
> - __xe_unpin_fb_vma(old_plane_state->ggtt_vma);
> - old_plane_state->ggtt_vma = NULL;
> + const struct intel_framebuffer *fb = to_intel_framebuffer(old_plane_state->hw.fb);
> +
> + if (!intel_fb_uses_dpt(&fb->base)) {
> + __xe_unpin_fb_vma(old_plane_state->ggtt_vma);
> +
> + old_plane_state->ggtt_vma = NULL;
> + } else {
> + xe_fb_pin_dpt_unpin(fb->dpt, old_plane_state->dpt_vma,
> + old_plane_state->ggtt_vma);
> +
> + old_plane_state->dpt_vma = NULL;
> + old_plane_state->ggtt_vma = NULL;
> + }
> }
>
> static void xe_fb_pin_get_map(struct i915_vma *vma, struct iosys_map *map)
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-04-24 10:12 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 16:53 [PATCH 00/16] drm/i915: Introduce 'fb_pin' parent interface Ville Syrjala
2026-04-23 16:53 ` [PATCH 01/16] drm/i915: Introduce intel_parent_fb_pin_get_map() Ville Syrjala
2026-04-24 9:14 ` Jani Nikula
2026-04-23 16:53 ` [PATCH 02/16] drm/i915: Move intel_fb_pin_params to the parent interface Ville Syrjala
2026-04-24 9:19 ` Jani Nikula
2026-04-23 16:53 ` [PATCH 03/16] drm/i915: Move the i915_dpt_offset()==0 assert Ville Syrjala
2026-04-24 9:19 ` Jani Nikula
2026-04-23 16:53 ` [PATCH 04/16] drm/i915: Reorganize intel_plane_pin_fb() a bit Ville Syrjala
2026-04-24 9:55 ` Jani Nikula
2026-04-23 16:53 ` [PATCH 05/16] drm/i915: Introduce i915_fb_pin_dpt_(un)pin() Ville Syrjala
2026-04-24 9:56 ` Jani Nikula
2026-04-23 16:53 ` [PATCH 06/16] drm/i915: Introduce i915_fb_pin_ggtt_(un)pin() Ville Syrjala
2026-04-24 9:59 ` Jani Nikula
2026-04-23 16:53 ` [PATCH 07/16] drm/xe: Move the FORCE_WC assert into __xe_pin_fb_vma() Ville Syrjala
2026-04-24 10:02 ` Jani Nikula
2026-04-23 16:53 ` [PATCH 08/16] drm/xe: Kill the fbdev vma reuse hack Ville Syrjala
2026-04-24 10:06 ` Jani Nikula
2026-04-23 16:53 ` [PATCH 09/16] drm/xe: Reorganize intel_plane_pin_fb() a bit Ville Syrjala
2026-04-24 10:07 ` Jani Nikula
2026-04-23 16:53 ` [PATCH 10/16] drm/xe: Introduce xe_fb_pin_dpt_(un)pin() Ville Syrjala
2026-04-24 10:12 ` Jani Nikula [this message]
2026-04-23 16:53 ` [PATCH 11/16] drm/xe: Introduce xe_fb_pin_ggtt_(un)pin() Ville Syrjala
2026-04-24 10:13 ` Jani Nikula
2026-04-23 16:53 ` [PATCH 12/16] drm/xe: Restructure reuse_vma() Ville Syrjala
2026-04-24 10:30 ` Jani Nikula
2026-04-30 16:19 ` [PATCH v2 " Ville Syrjala
2026-04-23 16:53 ` [PATCH 13/16] drm/i915: Introduce the main fb_pin parent interface Ville Syrjala
2026-04-24 10:48 ` Jani Nikula
2026-04-24 10:55 ` Ville Syrjälä
2026-04-23 16:53 ` [PATCH 14/16] drm/i915/fbdev: Use intel_parent_fb_pin_ggtt_(un)pin() Ville Syrjala
2026-04-24 12:54 ` Jani Nikula
2026-04-23 16:53 ` [PATCH 15/16] drm/xe: Use xe_fb_pin_ggtt_pin() for the initial FB pin Ville Syrjala
2026-04-24 12:58 ` Jani Nikula
2026-04-23 16:53 ` [PATCH 16/16] drm/i915: Consolidate the intel_plane_(un)pin_fb() implementations Ville Syrjala
2026-04-24 13:30 ` Jani Nikula
2026-04-27 12:08 ` Ville Syrjälä
2026-04-23 17:01 ` ✗ CI.checkpatch: warning for drm/i915: Introduce 'fb_pin' parent interface Patchwork
2026-04-23 17:02 ` ✓ CI.KUnit: success " Patchwork
2026-04-30 18:10 ` ✗ CI.checkpatch: warning for drm/i915: Introduce 'fb_pin' parent interface (rev2) Patchwork
2026-04-30 18:11 ` ✓ CI.KUnit: success " Patchwork
2026-04-30 19:15 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-05-01 6:29 ` ✓ Xe.CI.FULL: success " Patchwork
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5c693619e1f9551c8cc8ad5cfce521e45216f574@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=ville.syrjala@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox