From: "Siddiqui, Ayaz A" <ayaz.siddiqui@intel.com>
To: Talla Raviteja Goud <ravitejax.gpud.talla@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Surendrakumar Upadhyay,
TejaskumarX" <tejaskumarx.surendrakumar.upadhyay@intel.com>,
"Meena, Mahesh" <mahesh.meena@intel.com>,
"Pandey, Hariom" <hariom.pandey@intel.com>
Cc: "Talla, RavitejaX Goud" <ravitejax.goud.talla@intel.com>,
"De Marchi, Lucas" <lucas.demarchi@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/adl_s: Remove require_force_probe protection
Date: Tue, 7 Sep 2021 05:43:52 +0000 [thread overview]
Message-ID: <CH0PR11MB5755559816096FECA929754FFCD39@CH0PR11MB5755.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210903182034.668467-1-ravitejax.gpud.talla@intel.com>
> -----Original Message-----
> From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf Of Talla
> Raviteja Goud
> Sent: Friday, September 3, 2021 11:51 PM
> To: intel-gfx@lists.freedesktop.org; Surendrakumar Upadhyay, TejaskumarX
> <tejaskumarx.surendrakumar.upadhyay@intel.com>; Meena, Mahesh
> <mahesh.meena@intel.com>; Pandey, Hariom <hariom.pandey@intel.com>
> Cc: Talla, RavitejaX Goud <ravitejax.goud.talla@intel.com>; De Marchi, Lucas
> <lucas.demarchi@intel.com>
> Subject: [Intel-gfx] [PATCH] drm/i915/adl_s: Remove require_force_probe
> protection
>
> From: ravitejax <ravitejax.goud.talla@intel.com>
>
> Removing force probe protection from ADLS platform. Did not observe
> warnings, errors, flickering or any visual defects while doing ordinary tasks
> like browsing and editing documents in a two monitor setup.
>
> For more info drm-tip idle run results :
> https://intel-gfx-ci.01.org/tree/drm-tip/bat-all.html?
>
> Cc: Lucas De Marchi <lucas.demarchi@intel.com>
> Signed-off-by: ravitejax <ravitejax.goud.talla@intel.com>
> ---
> 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 03a820955458..d4a6a9dcf182
> 100644
> --- a/drivers/gpu/drm/i915/i915_pci.c
> +++ b/drivers/gpu/drm/i915/i915_pci.c
> @@ -912,7 +912,6 @@ static const struct intel_device_info adl_s_info = {
> GEN12_FEATURES,
> PLATFORM(INTEL_ALDERLAKE_S),
> .pipe_mask = BIT(PIPE_A) | BIT(PIPE_B) | BIT(PIPE_C) | BIT(PIPE_D),
> - .require_force_probe = 1,
AFIR, force probe removal was blocked for MOCS update, which is landed on drm-tip.
LGTM.
Reviewed-by: Ayaz A Siddiqui <ayaz.siddiqui@intel.com>
> .display.has_hti = 1,
> .display.has_psr_hw_tracking = 0,
> .platform_engine_mask =
> --
> 2.30.2
next prev parent reply other threads:[~2021-09-07 5:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 18:20 [Intel-gfx] [PATCH] drm/i915/adl_s: Remove require_force_probe protection Talla Raviteja Goud
2021-09-03 19:09 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2021-09-03 22:19 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-09-06 8:24 ` [Intel-gfx] ✓ Fi.CI.BAT: " Patchwork
2021-09-06 9:43 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-09-07 5:43 ` Siddiqui, Ayaz A [this message]
2021-09-08 14:23 ` [Intel-gfx] [PATCH] " Joonas Lahtinen
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=CH0PR11MB5755559816096FECA929754FFCD39@CH0PR11MB5755.namprd11.prod.outlook.com \
--to=ayaz.siddiqui@intel.com \
--cc=hariom.pandey@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=mahesh.meena@intel.com \
--cc=ravitejax.goud.talla@intel.com \
--cc=ravitejax.gpud.talla@intel.com \
--cc=tejaskumarx.surendrakumar.upadhyay@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;
as well as URLs for NNTP newsgroup(s).