All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Sousa <gustavo.sousa@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>,
	<intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH v3 5/8] drm/xe: Call xe_wa_process_device_oob() after xe_sriov_probe_early()
Date: Mon, 9 Mar 2026 18:24:35 -0300	[thread overview]
Message-ID: <87qzpsae7g.fsf@intel.com> (raw)
In-Reply-To: <39d0a9dc-0e17-4571-8ab8-7abac07e6196@intel.com>

Michal Wajdeczko <michal.wajdeczko@intel.com> writes:

> On 3/9/2026 9:07 PM, Gustavo Sousa wrote:
>> We will need to use FUNC(xe_rtp_match_not_sriov_vf) in an upcoming
>> device OOB workaround and we need the SRIOV mode already defined by the
>> time that workaround check is done.  Move the call to
>> xe_wa_process_device_oob() to happen after  xe_sriov_probe_early() to
>> allow usage of FUNC(xe_rtp_match_not_sriov_vf).
>> 
>> Signed-off-by: Gustavo Sousa <gustavo.sousa@intel.com>
>> ---
>>  drivers/gpu/drm/xe/xe_device.c | 6 +++---
>>  1 file changed, 3 insertions(+), 3 deletions(-)
>> 
>> diff --git a/drivers/gpu/drm/xe/xe_device.c b/drivers/gpu/drm/xe/xe_device.c
>> index 3462645ca13c..5651bcdc6752 100644
>> --- a/drivers/gpu/drm/xe/xe_device.c
>> +++ b/drivers/gpu/drm/xe/xe_device.c
>> @@ -699,15 +699,15 @@ int xe_device_probe_early(struct xe_device *xe)
>>  {
>>  	int err;
>>  
>> -	xe_wa_device_init(xe);
>> -	xe_wa_process_device_oob(xe);
>> -
>>  	err = xe_mmio_probe_early(xe);
>>  	if (err)
>>  		return err;
>>  
>>  	xe_sriov_probe_early(xe);
>>  
>> +	xe_wa_device_init(xe);
>> +	xe_wa_process_device_oob(xe);
>
> maybe it would be better to move wa_init after below vf_update call
> to keep SRIOV related functions together ? also the vf_update will
> clear some feature flags, maybe it's also better to do that before
> any wa processing?

I don't think there are device OOB workarounds that need that
information right now, but, yeah, keeping SRIOV-related functions
together sounds fair.

--
Gustavo Sousa

>
>> +
>>  	if (IS_SRIOV_VF(xe))
>>  		vf_update_device_info(xe);
>>  
>> 

  reply	other threads:[~2026-03-09 21:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-09 20:07 [PATCH v3 0/8] Extra enabling patches for NVL-P Gustavo Sousa
2026-03-09 20:07 ` [PATCH v3 1/8] drm/xe: Modify stepping info directly in xe_step_*_get() Gustavo Sousa
2026-03-09 20:07 ` [PATCH v3 2/8] drm/xe: Drop unused IS_PLATFORM_STEP() and IS_SUBPLATFORM_STEP() Gustavo Sousa
2026-03-09 20:07 ` [PATCH v3 3/8] drm/xe/nvlp: Read platform-level stepping info Gustavo Sousa
2026-03-09 20:07 ` [PATCH v3 4/8] drm/xe/rtp: Add support for matching platform-level stepping Gustavo Sousa
2026-03-09 20:07 ` [PATCH v3 5/8] drm/xe: Call xe_wa_process_device_oob() after xe_sriov_probe_early() Gustavo Sousa
2026-03-09 20:19   ` Matt Roper
2026-03-09 20:20   ` Michal Wajdeczko
2026-03-09 21:24     ` Gustavo Sousa [this message]
2026-03-09 20:07 ` [PATCH v3 6/8] drm/xe/nvlp: Implement Wa_14026539277 Gustavo Sousa
2026-03-09 20:13   ` Matt Roper
2026-03-09 20:07 ` [PATCH v3 7/8] drm/xe/xe3p: Drop Wa_16028780921 Gustavo Sousa
2026-03-09 20:07 ` [PATCH v3 8/8] drm/xe: Translate C-state "reset value" into RC6 Gustavo Sousa
2026-03-09 20:14 ` ✓ CI.KUnit: success for Extra enabling patches for NVL-P (rev3) Patchwork
2026-03-09 21:02 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-03-09 22:03   ` Gustavo Sousa
2026-03-09 22:08     ` Matt Roper
2026-03-09 22:24       ` Gustavo Sousa

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=87qzpsae7g.fsf@intel.com \
    --to=gustavo.sousa@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=michal.wajdeczko@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.