From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/mtl: Drop force_probe requirement
Date: Wed, 6 Sep 2023 10:08:12 -0400 [thread overview]
Message-ID: <ZPiHzDymgI+kMRMc@intel.com> (raw)
In-Reply-To: <ZPhFj0H8OYtp1CGh@ashyti-mobl2.lan>
On Wed, Sep 06, 2023 at 11:25:35AM +0200, Andi Shyti wrote:
> Hi Radhakrishna,
>
> On Tue, Sep 05, 2023 at 12:36:24PM -0700, Radhakrishna Sripada wrote:
> > Meteorlake has been very usable for a while now, all of uapi changes
> > related to fundamental platform usage have been finalized and all
> > required firmware blobs are available. Recent CI results have also
> > been healthy, so we're ready to drop the force_probe requirement and
> > enable the platform by default.
> >
> > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
> > Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> > Cc: Jani Nikula <jani.nikula@linux.intel.com>
> > Signed-off-by: Radhakrishna Sripada <radhakrishna.sripada@intel.com>
>
> Please keep me in the loop as well... It's been a year I've been
> working for this patch to work :)
>
> > ---
> > drivers/gpu/drm/i915/i915_pci.c | 1 -
> > 1 file changed, 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/i915/i915_pci.c b/drivers/gpu/drm/i915/i915_pci.c
> > index df7c261410f7..fe748906c06f 100644
> > --- a/drivers/gpu/drm/i915/i915_pci.c
> > +++ b/drivers/gpu/drm/i915/i915_pci.c
> > @@ -836,7 +836,6 @@ static const struct intel_device_info mtl_info = {
> > .has_pxp = 1,
> > .memory_regions = REGION_SMEM | REGION_STOLEN_LMEM,
> > .platform_engine_mask = BIT(RCS0) | BIT(BCS0) | BIT(CCS0),
> > - .require_force_probe = 1,
>
> What's the thinking behind this patch? Are you trying to
> understand how CI behaves?
CI uses kernel config to force_probe. MTL is already being tested there.
Also there's no 'CI' or 'HAX' tag on this patch.
So I would assume this is the ask to remove the protection.
But based on this question from Andi and knowing that he is working on
the MTL w/a I'm assuming that this is not the right time yet to remove
this protection.
Please ensure all the diligence is taken before sending this patch again.
Also ensure that the current CI failures are fixed (gt_pm and gt_engines)
and that CI has a stable green picture.
Thanks,
Rodrigo.
>
> Andi
>
> > MTL_CACHELEVEL,
> > };
> >
> > --
> > 2.34.1
next prev parent reply other threads:[~2023-09-06 14:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 19:36 [Intel-gfx] [PATCH] drm/i915/mtl: Drop force_probe requirement Radhakrishna Sripada
2023-09-06 2:11 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-09-06 4:05 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-09-06 9:25 ` [Intel-gfx] [PATCH] " Andi Shyti
2023-09-06 9:29 ` Andi Shyti
2023-09-06 14:08 ` Rodrigo Vivi [this message]
2023-09-07 2:05 ` Sripada, Radhakrishna
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=ZPiHzDymgI+kMRMc@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@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