Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Sousa <gustavo.sousa@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: intel-xe@lists.freedesktop.org,
	"Jani Nikula" <jani.nikula@linux.intel.com>,
	"Matthew Brost" <matthew.brost@intel.com>,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Subject: Re: [PATCH] drm/xe/nvlp: Drop force_probe requirement
Date: Thu, 12 Nov 2026 18:46:36 -0300	[thread overview]
Message-ID: <87y0axn2o3.fsf@intel.com> (raw)
In-Reply-To: <avSKcvEXGAsoJLEo@intel.com>

Rodrigo Vivi <rodrigo.vivi@intel.com> writes:

> On Tue, Nov 10, 2026 at 07:52:23PM -0300, Gustavo Sousa wrote:
>> NVL-P is stable enough for us to drop force_probe requirement. Let's
>> do that.
>> 
>> Cc: Jani Nikula <jani.nikula@linux.intel.com>
>> Cc: Matthew Brost <matthew.brost@intel.com>
>> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
>> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
>> Signed-off-by: Gustavo Sousa <gustavo.sousa@intel.com>
>
> Acked-by: Rodrigo Vivi <rodrigo.vivi@intel.com>

Applied to drm-xe-next. Thanks Rodrigo for the ack!

--
Gustavo Sousa

>
>> ---
>>  drivers/gpu/drm/xe/xe_pci.c | 1 -
>>  1 file changed, 1 deletion(-)
>> 
>> diff --git a/drivers/gpu/drm/xe/xe_pci.c b/drivers/gpu/drm/xe/xe_pci.c
>> index be1b063cb68d..fefa600b7ff7 100644
>> --- a/drivers/gpu/drm/xe/xe_pci.c
>> +++ b/drivers/gpu/drm/xe/xe_pci.c
>> @@ -508,7 +508,6 @@ static const struct xe_device_desc nvlp_desc = {
>>  	.has_sriov = true,
>>  	.max_gt_per_tile = 2,
>>  	MULTI_LRC_MASK,
>> -	.require_force_probe = true,
>>  	.va_bits = 48,
>>  	.vm_max_level = 4,
>>  };
>> 
>> ---
>> base-commit: a6a3cf6cc0759788b1b0ce63f9cfd855d5785449
>> change-id: 20261110-nvlp-drop-force_probe-requirement-7deab7e4e3cc
>> 
>> Best regards,
>> --  
>> Gustavo Sousa <gustavo.sousa@intel.com>
>> 

      reply	other threads:[~2026-11-12 21:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-10 22:52 [PATCH] drm/xe/nvlp: Drop force_probe requirement Gustavo Sousa
2026-11-10 23:01 ` ✓ CI.KUnit: success for " Patchwork
2026-11-10 23:36 ` ✓ Xe.CI.BAT: " Patchwork
2026-11-11  2:15 ` [PATCH] " sashiko-bot
2026-11-11  2:53 ` ✓ Xe.CI.FULL: success for " Patchwork
2026-11-11 15:32 ` [PATCH] " Rodrigo Vivi
2026-11-12 21:46   ` Gustavo Sousa [this message]

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=87y0axn2o3.fsf@intel.com \
    --to=gustavo.sousa@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=matthew.brost@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=thomas.hellstrom@linux.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