From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
To: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
Cc: <intel-xe@lists.freedesktop.org>, <badal.nilawar@intel.com>,
<anoop.c.vijay@intel.com>
Subject: Re: [PATCH v8 3/3] drm/xe/soc_remapper: Add system controller config for SoC remapper
Date: Wed, 25 Mar 2026 10:24:25 -0700 [thread overview]
Message-ID: <acQaSeCyFifXFtOt@soc-5CG1426VCC.clients.intel.com> (raw)
In-Reply-To: <85fr5o9cle.wl-ashutosh.dixit@intel.com>
On Wed, Mar 25, 2026 at 08:02:21AM -0700, Dixit, Ashutosh wrote:
>On Tue, 23 Dec 2025 10:39:47 -0800, Umesh Nerlige Ramappa wrote:
>>
>> @@ -30,10 +36,17 @@ static void xe_soc_remapper_set_telem_region(struct xe_device *xe, u32 index)
>> */
>> int xe_soc_remapper_init(struct xe_device *xe)
>> {
>> - if (xe->info.has_soc_remapper_telem) {
>> + bool has_soc_remapper = xe->info.has_soc_remapper_telem ||
>> + xe->info.has_soc_remapper_sysctrl;
>> +
>> + if (has_soc_remapper)
>> spin_lock_init(&xe->soc_remapper.lock);
>> +
>> + if (xe->info.has_soc_remapper_telem)
>> xe->soc_remapper.set_telem_region = xe_soc_remapper_set_telem_region;
>> - }
>> +
>> + if (xe->info.has_soc_remapper_sysctrl)
>> + xe->soc_remapper.set_sysctrl_region = xe_soc_remapper_set_sysctrl_region;
>
>Maybe these if () statements hould be moved inside these functions?
>Otherwise they will need to replicated in every place these functions are
>called?
The idea was for the caller to check if the funcs are available and then
deal with the outcome. In sysctrl, the check was changed to assert due
to some review comments. We are trying to change it back to a check and
that should do for now. The telem caller is checking for it and bailing
out as needed.
These function pointers are a bit off in terms of implementation. Matt
Brost had suggested to clean them up and use vfuncs instead, but that
refactor is still in the works.
Thanks,
Umesh
>
>We've already seen this problem in the sysctrl series.
next prev parent reply other threads:[~2026-03-25 17:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 18:39 [PATCH v8 0/3] Add SoC remapper support for system controller Umesh Nerlige Ramappa
2025-12-23 18:39 ` [PATCH v8 1/3] drm/xe/soc_remapper: Initialize SoC remapper during Xe probe Umesh Nerlige Ramappa
2025-12-23 18:39 ` [PATCH v8 2/3] drm/xe/soc_remapper: Use SoC remapper helper from VSEC code Umesh Nerlige Ramappa
2025-12-23 18:39 ` [PATCH v8 3/3] drm/xe/soc_remapper: Add system controller config for SoC remapper Umesh Nerlige Ramappa
2026-03-25 15:02 ` Dixit, Ashutosh
2026-03-25 17:24 ` Umesh Nerlige Ramappa [this message]
2025-12-23 18:45 ` ✗ CI.checkpatch: warning for Add SoC remapper support for system controller (rev8) Patchwork
2025-12-23 18:46 ` ✓ CI.KUnit: success " Patchwork
2025-12-23 19:42 ` ✓ Xe.CI.BAT: " Patchwork
2025-12-24 5:28 ` ✗ Xe.CI.Full: failure " 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=acQaSeCyFifXFtOt@soc-5CG1426VCC.clients.intel.com \
--to=umesh.nerlige.ramappa@intel.com \
--cc=anoop.c.vijay@intel.com \
--cc=ashutosh.dixit@intel.com \
--cc=badal.nilawar@intel.com \
--cc=intel-xe@lists.freedesktop.org \
/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