From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Subject: [PATCH 3/3] drm/i915/display: Allowing looking up invalid modifiers to make xe happy
Date: Wed, 21 Aug 2024 22:47:50 +0200 [thread overview]
Message-ID: <20240821204750.539075-4-maarten.lankhorst@linux.intel.com> (raw)
In-Reply-To: <20240821204750.539075-1-maarten.lankhorst@linux.intel.com>
Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
---
drivers/gpu/drm/i915/display/intel_fb.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/gpu/drm/i915/display/intel_fb.c b/drivers/gpu/drm/i915/display/intel_fb.c
index f23547a88b1fb..951a0f3fa6aaa 100644
--- a/drivers/gpu/drm/i915/display/intel_fb.c
+++ b/drivers/gpu/drm/i915/display/intel_fb.c
@@ -382,6 +382,10 @@ bool intel_fb_is_tiled_modifier(u64 modifier)
*/
bool intel_fb_is_ccs_modifier(u64 modifier)
{
+ struct intel_modifier_desc *desc = lookup_modifier_or_null(modifier);
+ if (!desc)
+ return false;
+
return plane_caps_contain_any(lookup_modifier(modifier)->plane_caps,
INTEL_PLANE_CAP_CCS_MASK);
}
--
2.45.2
next prev parent reply other threads:[~2024-08-21 20:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 20:47 [PATCH 0/3] drm/xe: Alternative CCS fix Maarten Lankhorst
2024-08-21 20:47 ` [PATCH 1/3] drm/xe: Align 64k scanout buffers physically when multiple of 64k Maarten Lankhorst
2024-08-21 20:47 ` [PATCH 2/3] drm/xe: Use 64K pages for scanout buffers for Battlemage Maarten Lankhorst
2024-08-21 20:47 ` Maarten Lankhorst [this message]
2024-08-21 20:53 ` ✓ CI.Patch_applied: success for drm/xe: Alternative CCS fix Patchwork
2024-08-21 20:54 ` ✗ CI.checkpatch: warning " Patchwork
2024-08-21 20:55 ` ✓ CI.KUnit: success " Patchwork
2024-08-21 21:00 ` ✗ CI.Build: failure " 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=20240821204750.539075-4-maarten.lankhorst@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
/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