From: Gustavo Sousa <gustavo.sousa@intel.com>
To: "Bhadane, Dnyaneshwar" <dnyaneshwar.bhadane@intel.com>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Cc: "Roper, Matthew D" <matthew.d.roper@intel.com>
Subject: RE: [PATCH 05/16] drm/xe/xe3p_lpg: Add MCR steering
Date: Tue, 3 Feb 2026 21:33:15 -0300 [thread overview]
Message-ID: <87ikcd73g4.fsf@intel.com> (raw)
In-Reply-To: <IA1PR11MB6266F2346F428242E7F37C50E29BA@IA1PR11MB6266.namprd11.prod.outlook.com>
"Bhadane, Dnyaneshwar" <dnyaneshwar.bhadane@intel.com> writes:
>> -----Original Message-----
>> From: Intel-xe <intel-xe-bounces@lists.freedesktop.org> On Behalf Of Gustavo
>> Sousa
>> Sent: Tuesday, February 3, 2026 3:13 AM
>> To: intel-xe@lists.freedesktop.org; intel-gfx@lists.freedesktop.org
>> Cc: Sousa, Gustavo <gustavo.sousa@intel.com>; Roper, Matthew D
>> <matthew.d.roper@intel.com>
>> Subject: [PATCH 05/16] drm/xe/xe3p_lpg: Add MCR steering
>>
>> From: Matt Roper <matthew.d.roper@intel.com>
>>
>> Xe3p_LPG has nearly identical steering to Xe2 and Xe3. The only DSS/XeCore
>> change from those IPs is an additional range from 0xDE00-0xDE7F that was
>> previously reserved, so we can simply grow one of the existing ranges in the Xe2
>> table to include it. Similarly, the "instance0" table is also almost identical, but
>> gains one additional PSMI range and requires a separate table.
>>
>> Bspec: 75242
>> Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
>> Signed-off-by: Gustavo Sousa <gustavo.sousa@intel.com>
>> ---
>> drivers/gpu/drm/xe/xe_gt_mcr.c | 18 +++++++++++++++++-
>> 1 file changed, 17 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_gt_mcr.c b/drivers/gpu/drm/xe/xe_gt_mcr.c
>> index 7c1fe9ac120d..b112e551fc79 100644
>> --- a/drivers/gpu/drm/xe/xe_gt_mcr.c
>> +++ b/drivers/gpu/drm/xe/xe_gt_mcr.c
>> @@ -201,7 +201,7 @@ static const struct xe_mmio_range
>> xe2lpg_dss_steering_table[] = {
>> { 0x009680, 0x0096FF }, /* DSS */
>> { 0x00D800, 0x00D87F }, /* SLICE */
>> { 0x00DC00, 0x00DCFF }, /* SLICE */
>> - { 0x00DE80, 0x00E8FF }, /* DSS (0xE000-0xE0FF reserved) */
>> + { 0x00DE00, 0x00E8FF }, /* DSS (0xE000-0xE0FF reserved) */
>> { 0x00E980, 0x00E9FF }, /* SLICE */
>> { 0x013000, 0x0133FF }, /* DSS (0x13000-0x131FF), SLICE (0x13200-
>> 0x133FF) */
>> {},
>> @@ -280,6 +280,19 @@ static const struct xe_mmio_range
>> xe3p_xpc_instance0_steering_table[] = {
>> {},
>> };
>>
>> +static const struct xe_mmio_range xe3p_lpg_instance0_steering_table[] = {
>> + { 0x004000, 0x004AFF }, /* GAM, rsvd, GAMWKR */
>> + { 0x008700, 0x00887F }, /* NODE */
>> + { 0x00B000, 0x00B3FF }, /* NODE, L3BANK */
>> + { 0x00B500, 0x00B6FF }, /* PSMI */
> Hi,
> Could we extend the range till 0x00BEFF ?
>> + { 0x00C800, 0x00CFFF }, /* GAM */
>> + { 0x00D880, 0x00D8FF }, /* NODE */
>> + { 0x00DD00, 0x00DDFF }, /* MEMPIPE */
> Same as we did here extend till reserved.
We usually only include a reserved range if the range is preceeded and
followed by MCR ranges of the same steering group.
This doesn't seem to be the case here.
--
Gustavo Sousa
next prev parent reply other threads:[~2026-02-04 0:33 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 21:43 [PATCH 00/16] Basic enabling patches for Xe3p_LPG and NVL-P Gustavo Sousa
2026-02-02 21:43 ` [PATCH 01/16] drm/xe/xe3p_lpg: Add support for graphics IP 35.10 Gustavo Sousa
2026-02-02 22:11 ` Matt Roper
2026-02-02 23:36 ` Matt Roper
2026-02-03 23:53 ` Gustavo Sousa
2026-02-02 21:43 ` [PATCH 02/16] drm/xe/xe3p_lpg: Add initial workarounds for graphics version 35.10 Gustavo Sousa
2026-02-02 22:47 ` Matt Roper
2026-02-04 0:25 ` Gustavo Sousa
2026-02-02 21:43 ` [PATCH 03/16] drm/xe/pat: Differentiate between primary and media for PTA Gustavo Sousa
2026-02-02 22:51 ` Matt Roper
2026-02-02 21:43 ` [PATCH 04/16] drm/xe/xe3p_lpg: Add new PAT table Gustavo Sousa
2026-02-05 17:05 ` Matt Atwood
2026-02-02 21:43 ` [PATCH 05/16] drm/xe/xe3p_lpg: Add MCR steering Gustavo Sousa
2026-02-03 10:32 ` Bhadane, Dnyaneshwar
2026-02-04 0:33 ` Gustavo Sousa [this message]
2026-02-06 8:29 ` Bhadane, Dnyaneshwar
2026-02-06 12:38 ` Gustavo Sousa
2026-02-02 21:43 ` [PATCH 06/16] drm/xe/xe3p_lpg: Add LRC parsing for additional RCS engine state Gustavo Sousa
2026-02-05 22:12 ` Matt Atwood
2026-02-02 21:43 ` [PATCH 07/16] drm/xe/xe3p_lpg: Disable reporting of context switch status to GHWSP Gustavo Sousa
2026-02-05 17:31 ` Matt Atwood
2026-02-02 21:43 ` [PATCH 08/16] drm/xe/xe3p_lpg: Drop unnecessary tuning settings Gustavo Sousa
2026-02-05 17:28 ` Matt Atwood
2026-02-02 21:43 ` [PATCH 09/16] drm/xe/xe3p_lpg: Extend 'group ID' mask size Gustavo Sousa
2026-02-04 12:18 ` Bhadane, Dnyaneshwar
2026-02-02 21:43 ` [PATCH 10/16] drm/xe/xe3p_lpg: Update LRC sizes Gustavo Sousa
2026-02-02 23:29 ` Matt Roper
2026-02-02 21:43 ` [PATCH 11/16] drm/xe/xe3p_lpg: Set STLB bank hash mode to 4KB Gustavo Sousa
2026-02-02 23:34 ` Matt Roper
2026-02-02 21:43 ` [PATCH 12/16] drm/xe/xe3p_lpg: Enable multi-queue feature Gustavo Sousa
2026-02-02 23:35 ` Matt Roper
2026-02-02 21:43 ` [PATCH 13/16] drm/xe/nvlp: Add NVL-P platform definition Gustavo Sousa
2026-02-02 23:48 ` Matt Roper
2026-02-04 12:59 ` Gustavo Sousa
2026-02-04 18:08 ` Matt Roper
2026-02-04 18:36 ` Gustavo Sousa
2026-02-02 21:43 ` [PATCH 14/16] drm/xe/nvlp: Attach MOCS table for nvlp Gustavo Sousa
2026-02-02 23:48 ` Matt Roper
2026-02-02 21:43 ` [PATCH 15/16] drm/i915/nvlp: Hook up display support Gustavo Sousa
2026-02-03 4:19 ` Kandpal, Suraj
2026-02-02 21:43 ` [PATCH 16/16] drm/xe/nvlp: Define GuC firmware for NVL-P Gustavo Sousa
2026-02-02 23:52 ` Matt Roper
2026-02-02 23:37 ` ✓ i915.CI.BAT: success for Basic enabling patches for Xe3p_LPG and NVL-P Patchwork
2026-02-03 7:48 ` ✓ i915.CI.Full: " 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=87ikcd73g4.fsf@intel.com \
--to=gustavo.sousa@intel.com \
--cc=dnyaneshwar.bhadane@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--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