From: Tejas Upadhyay <tejaskumarx.surendrakumar.upadhyay@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH] drm/i915/ehl: Remove require_force_probe protection
Date: Tue, 29 Jun 2021 16:19:54 +0530 [thread overview]
Message-ID: <20210629104954.927151-1-tejaskumarx.surendrakumar.upadhyay@intel.com> (raw)
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.
For more info drm-tip idle run results :
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip.html?
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Signed-off-by: Tejas Upadhyay <tejaskumarx.surendrakumar.upadhyay@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 f1f43192f9fb..7d472611a190 100644
--- a/drivers/gpu/drm/i915/i915_pci.c
+++ b/drivers/gpu/drm/i915/i915_pci.c
@@ -845,7 +845,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,
};
--
2.31.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2021-06-29 10:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 10:49 Tejas Upadhyay [this message]
2021-06-29 11:53 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/ehl: Remove require_force_probe protection (rev2) Patchwork
2021-06-29 13:01 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-06-29 15:18 ` [Intel-gfx] [PATCH] drm/i915/ehl: Remove require_force_probe protection Rodrigo Vivi
2021-06-29 15:20 ` Rodrigo Vivi
-- strict thread matches above, loose matches on Subject: below --
2020-10-06 14:56 Kamati Srinivas
2020-10-06 17:46 ` Souza, Jose
2020-10-06 17:48 ` 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=20210629104954.927151-1-tejaskumarx.surendrakumar.upadhyay@intel.com \
--to=tejaskumarx.surendrakumar.upadhyay@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).