From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: "Jouni Högander" <jouni.hogander@intel.com>,
intel-xe@lists.freedesktop.org
Cc: Jani Nikula <jani.nikula@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-xe] [PATCH v2 0/5] FBC refactoring
Date: Tue, 12 Sep 2023 18:22:40 +0200 [thread overview]
Message-ID: <4a223d04-6578-9ebb-59b4-92e8bbf955b5@linux.intel.com> (raw)
In-Reply-To: <20230831095154.3121578-1-jouni.hogander@intel.com>
Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
On 2023-08-31 11:51, Jouni Högander wrote:
> These patches are cleaning up all #ifdefs added into intel_fbc.c for
> Xe build. I915 part of the refactoring is already merged into drm-tip
> and these patches are implementing interfaces or adding empty defines
> for Xe.
>
> v2: Add parenthesis around parameter in i915_gem_stolen_node_allocated
>
> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Cc: Uma Shankar <uma.shankar@intel.com>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
>
> Jouni Högander (5):
> Revert "drm/i915/display: Implement FBC support"
> fixup! drm/i915/display: Remaining changes to make xe compile
> drm/xe: Xe stolen memory handling for fbc support
> drm/xe: Add i915_gem.h compatibility header
> drm/xe: Add Xe implementation for fence checks used by fbc code
>
> drivers/gpu/drm/i915/display/intel_fbc.c | 101 +++---------------
> .../gpu/drm/xe/compat-i915-headers/i915_drv.h | 3 +
> .../gpu/drm/xe/compat-i915-headers/i915_gem.h | 9 ++
> .../xe/compat-i915-headers/i915_gem_stolen.h | 79 ++++++++++++++
> .../gpu/drm/xe/compat-i915-headers/i915_vma.h | 1 +
> .../xe/compat-i915-headers/intel_gt_types.h | 11 ++
> 6 files changed, 115 insertions(+), 89 deletions(-)
> create mode 100644 drivers/gpu/drm/xe/compat-i915-headers/i915_gem.h
> create mode 100644 drivers/gpu/drm/xe/compat-i915-headers/i915_gem_stolen.h
> create mode 100644 drivers/gpu/drm/xe/compat-i915-headers/intel_gt_types.h
>
next prev parent reply other threads:[~2023-09-12 16:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 9:51 [Intel-xe] [PATCH v2 0/5] FBC refactoring Jouni Högander
2023-08-31 9:51 ` [Intel-xe] [PATCH v2 1/5] Revert "drm/i915/display: Implement FBC support" Jouni Högander
2023-08-31 9:51 ` [Intel-xe] [PATCH v2 2/5] fixup! drm/i915/display: Remaining changes to make xe compile Jouni Högander
2023-08-31 9:51 ` [Intel-xe] [PATCH v2 3/5] drm/xe: Xe stolen memory handling for fbc support Jouni Högander
2023-08-31 9:51 ` [Intel-xe] [PATCH v2 4/5] drm/xe: Add i915_gem.h compatibility header Jouni Högander
2023-08-31 9:51 ` [Intel-xe] [PATCH v2 5/5] drm/xe: Add Xe implementation for fence checks used by fbc code Jouni Högander
2023-08-31 12:38 ` [Intel-xe] ✓ CI.Patch_applied: success for FBC refactoring (rev3) Patchwork
2023-08-31 12:39 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-08-31 12:40 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-08-31 12:47 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-08-31 12:47 ` [Intel-xe] ✗ CI.Hooks: failure " Patchwork
2023-08-31 12:47 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-08-31 13:21 ` [Intel-xe] ✓ CI.BAT: success " Patchwork
2023-09-12 16:22 ` Maarten Lankhorst [this message]
2023-09-14 5:40 ` [Intel-xe] [PATCH v2 0/5] FBC refactoring Hogander, Jouni
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=4a223d04-6578-9ebb-59b4-92e8bbf955b5@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=jouni.hogander@intel.com \
--cc=rodrigo.vivi@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