From: Lucas De Marchi <lucas.demarchi@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Lucas De Marchi <lucas.demarchi@intel.com>,
fei.yang@intel.com, Matt Roper <matthew.d.roper@intel.com>
Subject: [PATCH 0/2] drm/xe: Tile address change
Date: Fri, 7 Nov 2025 10:23:43 -0800 [thread overview]
Message-ID: <20251107-tile-addr-v1-0-a3014aadc2e7@intel.com> (raw)
Same patch as https://lore.kernel.org/all/20250930232645.600251-1-fei.yang@intel.com/
but with the additional suggestions taken care of, one of them as
a separate patch.
Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
---
Fei Yang (1):
drm/xe: Use SG_TILE_ADDR_RANGE instead of TILE_ADDR_RANGE
Lucas De Marchi (1):
drm/xe/vram: Move forcewake down to get_flat_ccs_offset()
drivers/gpu/drm/xe/regs/xe_gt_regs.h | 1 -
drivers/gpu/drm/xe/regs/xe_regs.h | 2 ++
drivers/gpu/drm/xe/xe_vram.c | 26 +++++++++++++++-----------
3 files changed, 17 insertions(+), 12 deletions(-)
base-commit: c52463739ee9b9e6cdc34d31aa705c75c82679ec
change-id: 20251107-tile-addr-39f7f5cfbd71
Lucas De Marchi
next reply other threads:[~2025-11-07 18:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 18:23 Lucas De Marchi [this message]
2025-11-07 18:23 ` [PATCH 1/2] drm/xe: Use SG_TILE_ADDR_RANGE instead of TILE_ADDR_RANGE Lucas De Marchi
2025-11-07 18:23 ` [PATCH 2/2] drm/xe/vram: Move forcewake down to get_flat_ccs_offset() Lucas De Marchi
2025-11-08 0:06 ` Matt Roper
2025-11-07 21:29 ` ✓ CI.KUnit: success for drm/xe: Tile address change Patchwork
2025-11-07 22:29 ` ✓ Xe.CI.BAT: " Patchwork
2025-11-09 4:55 ` ✗ Xe.CI.Full: failure " Patchwork
2025-11-10 17:43 ` [PATCH 0/2] " Lucas De Marchi
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=20251107-tile-addr-v1-0-a3014aadc2e7@intel.com \
--to=lucas.demarchi@intel.com \
--cc=fei.yang@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.d.roper@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;
as well as URLs for NNTP newsgroup(s).