From: Ville Syrjala <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: intel-xe@lists.freedesktop.org, Jani Nikula <jani.nikula@intel.com>
Subject: [PATCH v2 07/16] drm/xe: Move the FORCE_WC assert into __xe_pin_fb_vma()
Date: Fri, 8 May 2026 17:34:17 +0300 [thread overview]
Message-ID: <20260508143426.26504-8-ville.syrjala@linux.intel.com> (raw)
In-Reply-To: <20260508143426.26504-1-ville.syrjala@linux.intel.com>
From: Ville Syrjälä <ville.syrjala@linux.intel.com>
No need to bother the higher level pinning code with the
FORCE_WC assert. Move it into the lower level function.
This also introduces the check to intel_fb_pin_to_ggtt(), which
(for the moment) is still used for the fbdev bo setup. But this
is all display stuff we're talking about here so having the check
is correct everywhere.
v2: Pimp the commit message a bit (Jani)
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
---
drivers/gpu/drm/xe/display/xe_fb_pin.c | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/xe/display/xe_fb_pin.c b/drivers/gpu/drm/xe/display/xe_fb_pin.c
index 1039058a7ed6..cb987b844385 100644
--- a/drivers/gpu/drm/xe/display/xe_fb_pin.c
+++ b/drivers/gpu/drm/xe/display/xe_fb_pin.c
@@ -329,6 +329,9 @@ static struct i915_vma *__xe_pin_fb_vma(struct drm_gem_object *obj, bool is_dpt,
struct drm_exec exec;
int ret = 0;
+ /* We reject creating !SCANOUT fb's, so this is weird.. */
+ drm_WARN_ON(bo->ttm.base.dev, !(bo->flags & XE_BO_FLAG_FORCE_WC));
+
if (!vma)
return ERR_PTR(-ENODEV);
@@ -474,7 +477,6 @@ int intel_plane_pin_fb(struct intel_plane_state *new_plane_state,
{
struct drm_framebuffer *fb = new_plane_state->hw.fb;
struct drm_gem_object *obj = intel_fb_bo(fb);
- struct xe_bo *bo = gem_to_xe_bo(obj);
struct i915_vma *vma;
struct intel_plane *plane = to_intel_plane(new_plane_state->uapi.plane);
struct intel_fb_pin_params pin_params = {
@@ -486,9 +488,6 @@ int intel_plane_pin_fb(struct intel_plane_state *new_plane_state,
if (reuse_vma(new_plane_state, old_plane_state))
return 0;
- /* We reject creating !SCANOUT fb's, so this is weird.. */
- drm_WARN_ON(bo->ttm.base.dev, !(bo->flags & XE_BO_FLAG_FORCE_WC));
-
vma = __xe_pin_fb_vma(obj, intel_fb_uses_dpt(fb), &pin_params);
if (IS_ERR(vma))
--
2.52.0
next prev parent reply other threads:[~2026-05-08 14:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 14:34 [PATCH v2 00/16] drm/i915: Introduce 'fb_pin' parent interface Ville Syrjala
2026-05-08 14:34 ` [PATCH v2 01/16] drm/i915: Introduce intel_parent_fb_pin_get_map() Ville Syrjala
2026-05-08 14:34 ` [PATCH v2 02/16] drm/i915: Move intel_fb_pin_params to the parent interface Ville Syrjala
2026-05-08 14:34 ` [PATCH v2 03/16] drm/i915: Move the i915_dpt_offset()==0 assert Ville Syrjala
2026-05-08 14:34 ` [PATCH v2 04/16] drm/i915: Reorganize intel_plane_pin_fb() a bit Ville Syrjala
2026-05-08 14:34 ` [PATCH v2 05/16] drm/i915: Introduce i915_fb_pin_dpt_(un)pin() Ville Syrjala
2026-05-08 14:34 ` [PATCH v2 06/16] drm/i915: Introduce i915_fb_pin_ggtt_(un)pin() Ville Syrjala
2026-05-08 14:34 ` Ville Syrjala [this message]
2026-05-08 14:34 ` [PATCH v2 08/16] drm/xe: Kill the fbdev vma reuse hack Ville Syrjala
2026-05-08 14:34 ` [PATCH v2 09/16] drm/xe: Reorganize intel_plane_pin_fb() a bit Ville Syrjala
2026-05-08 14:34 ` [PATCH v2 10/16] drm/xe: Introduce xe_fb_pin_dpt_(un)pin() Ville Syrjala
2026-05-08 14:34 ` [PATCH v2 11/16] drm/xe: Introduce xe_fb_pin_ggtt_(un)pin() Ville Syrjala
2026-05-08 14:34 ` [PATCH v2 12/16] drm/xe: Restructure reuse_vma() Ville Syrjala
2026-05-08 14:34 ` [PATCH v2 13/16] drm/i915: Introduce the main fb_pin parent interface Ville Syrjala
2026-05-08 14:34 ` [PATCH v2 14/16] drm/i915/fbdev: Use intel_parent_fb_pin_ggtt_(un)pin() Ville Syrjala
2026-05-08 14:34 ` [PATCH v2 15/16] drm/xe: Use xe_fb_pin_ggtt_pin() for the initial FB pin Ville Syrjala
2026-05-08 14:34 ` [PATCH v2 16/16] drm/i915: Consolidate the intel_plane_(un)pin_fb() implementations Ville Syrjala
2026-05-08 17:26 ` ✓ i915.CI.BAT: success for drm/i915: Introduce 'fb_pin' parent interface (rev3) Patchwork
2026-05-09 15:15 ` ✓ i915.CI.Full: " 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=20260508143426.26504-8-ville.syrjala@linux.intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@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