All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Matt Atwood <matthew.s.atwood@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe/ptl: Drop force_probe requirement
Date: Tue, 8 Jul 2025 09:59:09 -0400	[thread overview]
Message-ID: <aG0kLU560CgQzyqi@intel.com> (raw)
In-Reply-To: <aGw9fMCuksw-pPoE@intel.com>

On Mon, Jul 07, 2025 at 05:34:52PM -0400, Rodrigo Vivi wrote:
> On Mon, Jul 07, 2025 at 01:19:59PM -0700, Matt Atwood wrote:
> > Panther Lake has proven to be stable through testing and use.
> > 
> > Remove the force_probe requirement and enable the platform by default.
> > 
> > Signed-off-by: Matt Atwood <matthew.s.atwood@intel.com>
> > ---
> > Panther Lake is running internal CI for the moment, but running upstream
> > branches. Tests show all greens and work in progress to get the machines
> > approved for moving to the upstream CI.
> 
> I was happy with the internal CI views that I saw last Friday.
> And I was almost acking this patch to move it through, but it
> looks we got some regression there that is blocking fw loading.
> So, let's keep the force_probe protection in place while the issue
> is investigated and getting fixed.

I take it back. Yesterday view was not a bad, but just a delayed view
with pending runs. All the runs completed and we have a green solid view.

I'm just pushed this patch to drm-xe-next. Let's continuously monitor
this green view and get these machines to the public CI asap.

Thanks,
Rodrigo.

> 
> > 
> >  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 e9c5d3150efc..ffd6ad569b7c 100644
> > --- a/drivers/gpu/drm/xe/xe_pci.c
> > +++ b/drivers/gpu/drm/xe/xe_pci.c
> > @@ -341,7 +341,6 @@ static const struct xe_device_desc ptl_desc = {
> >  	.has_display = true,
> >  	.has_sriov = true,
> >  	.max_gt_per_tile = 2,
> > -	.require_force_probe = true,
> >  	.needs_scratch = true,
> >  };
> >  
> > -- 
> > 2.49.0
> > 

  reply	other threads:[~2025-07-08 13:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-07 20:19 [PATCH] drm/xe/ptl: Drop force_probe requirement Matt Atwood
2025-07-07 20:54 ` ✓ CI.KUnit: success for " Patchwork
2025-07-07 21:33 ` ✓ Xe.CI.BAT: " Patchwork
2025-07-07 21:34 ` [PATCH] " Rodrigo Vivi
2025-07-08 13:59   ` Rodrigo Vivi [this message]
2025-07-08  0:43 ` ✗ Xe.CI.Full: failure for " 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=aG0kLU560CgQzyqi@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.s.atwood@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.