From: "Souza, Jose" <jose.souza@intel.com>
To: "Ausmus, James" <james.ausmus@intel.com>,
"Nikula, Jani" <jani.nikula@intel.com>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
"Roper, Matthew D" <matthew.d.roper@intel.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"Pandey, Hariom" <hariom.pandey@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"K, SrinivasX" <srinivasx.k@intel.com>,
"Surendrakumar Upadhyay,
TejaskumarX" <tejaskumarx.surendrakumar.upadhyay@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/ehl: Remove require_force_probe protection
Date: Tue, 6 Oct 2020 17:46:45 +0000 [thread overview]
Message-ID: <2f7809798dd0b59246d67c5044dafb1e518fc4c5.camel@intel.com> (raw)
In-Reply-To: <20201006145632.117291-1-srinivasx.k@intel.com>
+Rodrigo and Jani
On Tue, 2020-10-06 at 14:56 +0000, Kamati Srinivas wrote:
> Removing force probe protection from EHL 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.
One of the requirements was also to have CI BAT all green and shards as green is possible but EHL don't show up in CI results, we actually have one
single EHL machine in CI but I guess it is not able to run all tests that shards do:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9097/filelist.html
>
> Signed-off-by: Kamati Srinivas <srinivasx.k@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 366ddfc8df6b..aa9c17a6851c 100644
> --- a/drivers/gpu/drm/i915/i915_pci.c
> +++ b/drivers/gpu/drm/i915/i915_pci.c
> @@ -841,7 +841,6 @@ static const struct intel_device_info icl_info = {
> static const struct intel_device_info ehl_info = {
> GEN11_FEATURES,
> PLATFORM(INTEL_ELKHARTLAKE),
> - .require_force_probe = 1,
> .platform_engine_mask = BIT(RCS0) | BIT(BCS0) | BIT(VCS0) | BIT(VECS0),
> .ppgtt_size = 36,
> };
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-10-06 17:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 14:56 [PATCH] drm/i915/ehl: Remove require_force_probe protection Kamati Srinivas
2020-10-06 17:46 ` Souza, Jose [this message]
2020-10-06 17:48 ` [Intel-gfx] " Chris Wilson
2020-10-06 17:55 ` Vivi, Rodrigo
2020-10-06 18:02 ` Souza, Jose
2020-10-09 8:31 ` K, SrinivasX
2020-10-09 13:38 ` Vivi, Rodrigo
2020-10-09 18:08 ` Pandey, Hariom
2020-10-15 8:41 ` K, SrinivasX
2020-10-19 18:29 ` Rodrigo Vivi
2020-10-19 18:33 ` Chris Wilson
[not found] ` <CO1PR11MB50750A169A14FCC84C70C936F61F0@CO1PR11MB5075.namprd11.prod.outlook.com>
[not found] ` <CO1PR11MB5075AAFA3500F4A3A610FC52F6170@CO1PR11MB5075.namprd11.prod.outlook.com>
2020-10-28 11:53 ` Vivi, Rodrigo
2020-10-28 11:55 ` Pandey, Hariom
2020-11-27 20:36 ` Chris Wilson
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=2f7809798dd0b59246d67c5044dafb1e518fc4c5.camel@intel.com \
--to=jose.souza@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hariom.pandey@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=james.ausmus@intel.com \
--cc=jani.nikula@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=srinivasx.k@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).