From: "Nilawar, Badal" <badal.nilawar@intel.com>
To: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>,
<intel-xe@lists.freedesktop.org>
Cc: <lucas.demarchi@intel.com>, <ashutosh.dixit@intel.com>
Subject: Re: [PATCH v2 1/4] drm/xe/soc_remapper: Initialize SoC remapper during Xe probe
Date: Wed, 26 Nov 2025 00:44:37 +0530 [thread overview]
Message-ID: <26c5d4da-8528-4c52-8871-f4aa76300e40@intel.com> (raw)
In-Reply-To: <20251117205315.1458477-7-umesh.nerlige.ramappa@intel.com>
On 18-11-2025 02:23, Umesh Nerlige Ramappa wrote:
> SoC remapper is used to map different HW functions in the SoC to their
> respective drivers. Initialize SoC remapper during driver load.
>
> Signed-off-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
> ---
> v2: (Ashutosh/Lucas)
> - s/remapper/soc_remapper/
> - return status from init during probe
> - reorder patches 1 and 2 from earlier series
> - fix copyright year
> ---
> drivers/gpu/drm/xe/Makefile | 1 +
> drivers/gpu/drm/xe/xe_device.c | 5 +++++
> drivers/gpu/drm/xe/xe_device_types.h | 6 ++++++
> drivers/gpu/drm/xe/xe_soc_remapper.c | 15 +++++++++++++++
> drivers/gpu/drm/xe/xe_soc_remapper.h | 15 +++++++++++++++
> 5 files changed, 42 insertions(+)
> create mode 100644 drivers/gpu/drm/xe/xe_soc_remapper.c
> create mode 100644 drivers/gpu/drm/xe/xe_soc_remapper.h
>
> diff --git a/drivers/gpu/drm/xe/Makefile b/drivers/gpu/drm/xe/Makefile
> index 8aa85c93b3d6..977b75336016 100644
> --- a/drivers/gpu/drm/xe/Makefile
> +++ b/drivers/gpu/drm/xe/Makefile
> @@ -110,6 +110,7 @@ xe-y += xe_bb.o \
> xe_range_fence.o \
> xe_reg_sr.o \
> xe_reg_whitelist.o \
> + xe_soc_remapper.o \
Maintain alphabetical order.
> xe_ring_ops.o \
> xe_rtp.o \
> xe_sa.o \
> diff --git a/drivers/gpu/drm/xe/xe_device.c b/drivers/gpu/drm/xe/xe_device.c
> index 9f2f19dc1fd3..0d51502af30e 100644
> --- a/drivers/gpu/drm/xe/xe_device.c
> +++ b/drivers/gpu/drm/xe/xe_device.c
> @@ -60,6 +60,7 @@
> #include "xe_psmi.h"
> #include "xe_pxp.h"
> #include "xe_query.h"
> +#include "xe_soc_remapper.h"
Maintain alphabetical order.
> #include "xe_shrinker.h"
> #include "xe_survivability_mode.h"
> #include "xe_sriov.h"
> @@ -911,6 +912,10 @@ int xe_device_probe(struct xe_device *xe)
>
> xe_nvm_init(xe);
>
> + err = xe_soc_remapper_init(xe);
> + if (err)
> + return err;
> +
> err = xe_heci_gsc_init(xe);
> if (err)
> return err;
> diff --git a/drivers/gpu/drm/xe/xe_device_types.h b/drivers/gpu/drm/xe/xe_device_types.h
> index a03cc83aa26f..de23fff3262c 100644
> --- a/drivers/gpu/drm/xe/xe_device_types.h
> +++ b/drivers/gpu/drm/xe/xe_device_types.h
> @@ -547,6 +547,12 @@ struct xe_device {
> struct mutex lock;
> } pmt;
>
> + /* @soc_remapper: SoC remapper object */
> + struct {
> + /* Serialize access to SoC Remapper's index registers */
> + spinlock_t lock;
> + } soc_remapper;
> +
> /**
> * @pm_callback_task: Track the active task that is running in either
> * the runtime_suspend or runtime_resume callbacks.
> diff --git a/drivers/gpu/drm/xe/xe_soc_remapper.c b/drivers/gpu/drm/xe/xe_soc_remapper.c
> new file mode 100644
> index 000000000000..f5a02abd6ab1
> --- /dev/null
> +++ b/drivers/gpu/drm/xe/xe_soc_remapper.c
> @@ -0,0 +1,15 @@
> +// SPDX-License-Identifier: MIT
> +/*
> + * Copyright © 2025 Intel Corporation
> + */
> +
> +#include <linux/spinlock.h>
> +
> +#include "xe_soc_remapper.h"
> +
Please add doc here
> +int xe_soc_remapper_init(struct xe_device *xe)
> +{
> +
SoC remapper is DGPU specific entity, should there be DGPU check here,
may be add has_soc_remapper flag?
Thanks,
Badal
> spin_lock_init(&xe->soc_remapper.lock);
> +
> + return 0;
> +}
> diff --git a/drivers/gpu/drm/xe/xe_soc_remapper.h b/drivers/gpu/drm/xe/xe_soc_remapper.h
> new file mode 100644
> index 000000000000..3cfd44f1fd74
> --- /dev/null
> +++ b/drivers/gpu/drm/xe/xe_soc_remapper.h
> @@ -0,0 +1,15 @@
> +/* SPDX-License-Identifier: MIT */
> +/*
> + * Copyright © 2025 Intel Corporation
> + */
> +
> +#ifndef _XE_SOC_REMAPPER_H_
> +#define _XE_SOC_REMAPPER_H_
> +
> +#include <linux/types.h>
> +
> +#include "xe_device_types.h"
> +
> +int xe_soc_remapper_init(struct xe_device *xe);
> +
> +#endif
next prev parent reply other threads:[~2025-11-25 19:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 20:53 [PATCH v2 0/4] Add SoC remapper support for system controller Umesh Nerlige Ramappa
2025-11-17 20:53 ` [PATCH v2 1/4] drm/xe/soc_remapper: Initialize SoC remapper during Xe probe Umesh Nerlige Ramappa
2025-11-25 19:14 ` Nilawar, Badal [this message]
2025-11-17 20:53 ` [PATCH v2 2/4] drm/xe/soc_remapper: Use SoC remapper herlper from VSEC code Umesh Nerlige Ramappa
2025-12-02 5:03 ` Nilawar, Badal
2025-12-02 20:35 ` Umesh Nerlige Ramappa
2025-11-17 20:53 ` [PATCH v2 3/4] drm/xe/soc_remapper: Add system controller config for SoC remapper Umesh Nerlige Ramappa
2025-11-17 20:53 ` [PATCH v2 4/4] drm/xe/remapper: Reprogram remapper index on PM resume events Umesh Nerlige Ramappa
2025-11-26 14:46 ` Nilawar, Badal
2025-12-02 21:00 ` Umesh Nerlige Ramappa
2025-11-17 20:59 ` ✗ CI.checkpatch: warning for Add SoC remapper support for system controller (rev2) Patchwork
2025-11-17 21:00 ` ✓ CI.KUnit: success " Patchwork
2025-11-17 21:58 ` ✓ Xe.CI.BAT: " Patchwork
2025-11-17 23:38 ` ✓ 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=26c5d4da-8528-4c52-8871-f4aa76300e40@intel.com \
--to=badal.nilawar@intel.com \
--cc=ashutosh.dixit@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--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