From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Matt Roper <matthew.d.roper@intel.com>, intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org, Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/dg2: Drop force_probe requirement
Date: Fri, 18 Nov 2022 20:29:46 +0000 [thread overview]
Message-ID: <651d4399-8ec5-5c75-a634-6ea3ed0f0231@linux.intel.com> (raw)
In-Reply-To: <20221109001328.732000-1-matthew.d.roper@intel.com>
On 09/11/2022 00:13, Matt Roper wrote:
> DG2 has been very usable for a while now, and all of the uapi changes
> related to fundamental platform usage have been finalized. 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: Matt Roper <matthew.d.roper@intel.com>
> ---
>
> There was some recent offline discussion questioning whether we'd fully
> identified the root cause of some historic CI failures, or whether it
> was possible we might still have a bug lurking somewhere causing
> sporadic failures. Let's use this patch to centralize discussion about
> any remaining concerns and make sure they're addressed before we apply
> this.
The two main issues were analysed and I am satisfied that they are
either very sporadic and with impact limited to i915/DG2, or sporadic
with impact limited to a small subset of DG2 functionality. Furthermore,
there are already fixes for both which seem most probably will be merged
inside the 6.2 fixes window. Therefore I agree that we can proceed with
dropping the force_probe protection. I also understand our upstream
maintainer has acked the plan to finish up in the fixes window.
Acked-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Regards,
Tvrtko
> 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 211913be40ce..0866300243aa 100644
> --- a/drivers/gpu/drm/i915/i915_pci.c
> +++ b/drivers/gpu/drm/i915/i915_pci.c
> @@ -1078,7 +1078,6 @@ static const struct intel_device_info dg2_info = {
> XE_LPD_FEATURES,
> .__runtime.cpu_transcoder_mask = BIT(TRANSCODER_A) | BIT(TRANSCODER_B) |
> BIT(TRANSCODER_C) | BIT(TRANSCODER_D),
> - .require_force_probe = 1,
> };
>
> static const struct intel_device_info ats_m_info = {
next prev parent reply other threads:[~2022-11-18 20:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 0:13 [Intel-gfx] [PATCH] drm/i915/dg2: Drop force_probe requirement Matt Roper
2022-11-09 2:48 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2022-11-09 2:48 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2022-11-09 3:11 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-11-09 8:34 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-11-18 20:29 ` Tvrtko Ursulin [this message]
2022-11-18 20:37 ` [Intel-gfx] [PATCH] " Rodrigo Vivi
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=651d4399-8ec5-5c75-a634-6ea3ed0f0231@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.d.roper@intel.com \
--cc=rodrigo.vivi@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