Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Casey Bowman <casey.g.bowman@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: thomas.hellstrom@linux.intel.com, lucas.demarchi@intel.com,
	chris@chris-wilson.co.uk
Subject: [Intel-gfx] [PATCH 0/2] Splitting intel-gtt calls for non-x86 platforms
Date: Fri, 18 Mar 2022 19:00:40 -0700	[thread overview]
Message-ID: <20220319020042.306649-1-casey.g.bowman@intel.com> (raw)

The intel-gtt module defines some functions used by i915, but they are
only supported by x86 platforms. In order to bring i915 to a more
arch-neutral state, we split out these functions and provide stubs in
the case of non-x86 builds.

There may be a better filename choice for the files used in splitting
the calls, it's very much open to discussion.

Casey Bowman (2):
  drm/i915: Require INTEL_GTT to depend on X86
  drm/i915/gt: Split intel-gtt functions by arch

 drivers/gpu/drm/i915/Kconfig                |   2 +-
 drivers/gpu/drm/i915/Makefile               |   2 +
 drivers/gpu/drm/i915/gt/intel_ggtt.c        |  97 +----------------
 drivers/gpu/drm/i915/gt/intel_gt.c          |   6 +-
 drivers/gpu/drm/i915/gt/intel_gtt.h         |  10 ++
 drivers/gpu/drm/i915/gt/intel_gtt_support.c | 113 ++++++++++++++++++++
 drivers/gpu/drm/i915/gt/intel_gtt_support.h |  39 +++++++
 7 files changed, 172 insertions(+), 97 deletions(-)
 create mode 100644 drivers/gpu/drm/i915/gt/intel_gtt_support.c
 create mode 100644 drivers/gpu/drm/i915/gt/intel_gtt_support.h

-- 
2.25.1


             reply	other threads:[~2022-03-19  2:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-19  2:00 Casey Bowman [this message]
2022-03-19  2:00 ` [Intel-gfx] [PATCH 1/2] drm/i915: Require INTEL_GTT to depend on X86 Casey Bowman
2022-03-19  3:40   ` Lucas De Marchi
2022-03-19 17:37     ` Casey Bowman
2022-03-19  2:00 ` [Intel-gfx] [PATCH 2/2] drm/i915/gt: Split intel-gtt functions by arch Casey Bowman
2022-03-19  3:39   ` Lucas De Marchi
2022-03-19 17:46     ` Casey Bowman
2022-03-22 11:31     ` Tvrtko Ursulin
2022-03-19  2:30 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Splitting intel-gtt calls for non-x86 platforms Patchwork
2022-03-19  2:31 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-03-19  3:11 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-03-19  4:26 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=20220319020042.306649-1-casey.g.bowman@intel.com \
    --to=casey.g.bowman@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=thomas.hellstrom@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