From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Cc: intel-xe@lists.freedesktop.org, badal.nilawar@intel.com
Subject: Re: [PATCH 0/4] Add SoC remapper support for system controller
Date: Wed, 05 Nov 2025 16:05:54 -0800 [thread overview]
Message-ID: <87a51058kd.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20251105234753.603647-6-umesh.nerlige.ramappa@intel.com>
On Wed, 05 Nov 2025 15:47:54 -0800, Umesh Nerlige Ramappa wrote:
>
> Add system controller configuration using SoC remapper for Xe3p.
>
> Signed-off-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
>
> Umesh Nerlige Ramappa (4):
> drm/xe/vsec: Refactor to move remapper logic outside vsec code
> drm/xe/remapper: Add lock to serialize access to remapper index
> registers
> drm/xe/remapper: Add system controller index for remapper
> drm/xe/remapper: Reprogram remapper index on PM resume events
>
> drivers/gpu/drm/xe/Makefile | 1 +
> drivers/gpu/drm/xe/regs/xe_pmt.h | 3 --
> drivers/gpu/drm/xe/regs/xe_remapper_regs.h | 14 ++++++
> drivers/gpu/drm/xe/xe_device.c | 2 +
> drivers/gpu/drm/xe/xe_device_types.h | 12 +++++
> drivers/gpu/drm/xe/xe_pm.c | 5 +++
> drivers/gpu/drm/xe/xe_remapper.c | 52 ++++++++++++++++++++++
> drivers/gpu/drm/xe/xe_remapper.h | 18 ++++++++
Drive by comment: Isn't xe_remapper* name too general? Maybe call the files
xe_soc_remapper* or something like that?
> drivers/gpu/drm/xe/xe_vsec.c | 5 +--
> 9 files changed, 106 insertions(+), 6 deletions(-)
> create mode 100644 drivers/gpu/drm/xe/regs/xe_remapper_regs.h
> create mode 100644 drivers/gpu/drm/xe/xe_remapper.c
> create mode 100644 drivers/gpu/drm/xe/xe_remapper.h
>
> --
> 2.43.0
>
next prev parent reply other threads:[~2025-11-06 0:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 23:47 [PATCH 0/4] Add SoC remapper support for system controller Umesh Nerlige Ramappa
2025-11-05 23:47 ` [PATCH 1/4] drm/xe/vsec: Refactor to move remapper logic outside vsec code Umesh Nerlige Ramappa
2025-11-06 17:08 ` Lucas De Marchi
2025-11-05 23:47 ` [PATCH 2/4] drm/xe/remapper: Add lock to serialize access to remapper index registers Umesh Nerlige Ramappa
2025-11-06 17:15 ` Lucas De Marchi
2025-11-05 23:47 ` [PATCH 3/4] drm/xe/remapper: Add system controller index for remapper Umesh Nerlige Ramappa
2025-11-05 23:47 ` [PATCH 4/4] drm/xe/remapper: Reprogram remapper index on PM resume events Umesh Nerlige Ramappa
2025-11-06 0:05 ` Dixit, Ashutosh [this message]
2025-11-06 1:49 ` ✗ CI.checkpatch: warning for Add SoC remapper support for system controller Patchwork
2025-11-06 1:50 ` ✓ CI.KUnit: success " Patchwork
2025-11-06 2:53 ` ✓ Xe.CI.BAT: " Patchwork
2025-11-06 16:49 ` ✓ Xe.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=87a51058kd.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=badal.nilawar@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=umesh.nerlige.ramappa@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).