Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Jouni Högander" <jouni.hogander@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: "Jouni Högander" <jouni.hogander@intel.com>
Subject: [Intel-xe] [PATCH v3 5/5] drm/xe: Add Xe implementation for fence checks used by fbc code
Date: Wed, 13 Sep 2023 12:54:12 +0300	[thread overview]
Message-ID: <20230913095412.3427407-6-jouni.hogander@intel.com> (raw)
In-Reply-To: <20230913095412.3427407-1-jouni.hogander@intel.com>

Xe doesn't support legacy fences. Implement legacy fence and fence
id checks accordingly.

Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
---
 drivers/gpu/drm/xe/compat-i915-headers/i915_drv.h     |  1 +
 drivers/gpu/drm/xe/compat-i915-headers/i915_vma.h     |  1 +
 .../gpu/drm/xe/compat-i915-headers/intel_gt_types.h   | 11 +++++++++++
 3 files changed, 13 insertions(+)
 create mode 100644 drivers/gpu/drm/xe/compat-i915-headers/intel_gt_types.h

diff --git a/drivers/gpu/drm/xe/compat-i915-headers/i915_drv.h b/drivers/gpu/drm/xe/compat-i915-headers/i915_drv.h
index 55d0d5c7a386..94ab0354185e 100644
--- a/drivers/gpu/drm/xe/compat-i915-headers/i915_drv.h
+++ b/drivers/gpu/drm/xe/compat-i915-headers/i915_drv.h
@@ -19,6 +19,7 @@
 #include "i915_gem_stolen.h"
 #include "i915_reg_defs.h"
 #include "i915_utils.h"
+#include "intel_gt_types.h"
 #include "intel_uncore.h"
 #include <linux/pm_runtime.h>
 
diff --git a/drivers/gpu/drm/xe/compat-i915-headers/i915_vma.h b/drivers/gpu/drm/xe/compat-i915-headers/i915_vma.h
index 3d8a1cc0b132..9424144b1b5a 100644
--- a/drivers/gpu/drm/xe/compat-i915-headers/i915_vma.h
+++ b/drivers/gpu/drm/xe/compat-i915-headers/i915_vma.h
@@ -18,4 +18,5 @@ struct i915_vma {
 
 #define i915_ggtt_clear_scanout(bo) do { } while (0)
 
+#define i915_vma_fence_id(vma) -1
 #endif
diff --git a/drivers/gpu/drm/xe/compat-i915-headers/intel_gt_types.h b/drivers/gpu/drm/xe/compat-i915-headers/intel_gt_types.h
new file mode 100644
index 000000000000..c15806d6c4f7
--- /dev/null
+++ b/drivers/gpu/drm/xe/compat-i915-headers/intel_gt_types.h
@@ -0,0 +1,11 @@
+/* SPDX-License-Identifier: MIT */
+/*
+ * Copyright © 2023 Intel Corporation
+ */
+
+#ifndef __INTEL_GT_TYPES__
+#define __INTEL_GT_TYPES__
+
+#define intel_gt_support_legacy_fencing(gt) 0
+
+#endif
-- 
2.34.1


  parent reply	other threads:[~2023-09-13  9:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-13  9:54 [Intel-xe] [PATCH v3 0/5] FBC refactoring Jouni Högander
2023-09-13  9:54 ` [Intel-xe] [PATCH v3 1/5] Revert "drm/i915/display: Implement FBC support" Jouni Högander
2023-09-13  9:54 ` [Intel-xe] [PATCH v3 2/5] fixup! drm/i915/display: Remaining changes to make xe compile Jouni Högander
2023-09-13  9:54 ` [Intel-xe] [PATCH v3 3/5] drm/xe: Xe stolen memory handling for fbc support Jouni Högander
2023-09-13  9:54 ` [Intel-xe] [PATCH v3 4/5] drm/xe: Add i915_gem.h compatibility header Jouni Högander
2023-09-14  9:45   ` Jani Nikula
2023-09-13  9:54 ` Jouni Högander [this message]
2023-09-13 10:36 ` [Intel-xe] ✓ CI.Patch_applied: success for FBC refactoring (rev4) Patchwork
2023-09-13 10:37 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-09-13 10:38 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-09-13 10:45 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-09-13 10:45 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-09-13 10:46 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-09-13 11:19 ` [Intel-xe] ✗ CI.BAT: failure " Patchwork
2023-09-13 14:32 ` [Intel-xe] ✓ CI.Patch_applied: success for FBC refactoring (rev5) Patchwork
2023-09-13 14:32 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-09-13 14:34 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-09-13 14:41 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-09-13 14:41 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-09-13 14:42 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-09-13 15:13 ` [Intel-xe] ✓ CI.BAT: 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=20230913095412.3427407-6-jouni.hogander@intel.com \
    --to=jouni.hogander@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