From: Anusha Srivatsa <anusha.srivatsa@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH] drm/i915/dg1: Remove require_force_probe protection
Date: Tue, 22 Feb 2022 10:19:37 -0800 [thread overview]
Message-ID: <20220222181937.592346-1-anusha.srivatsa@intel.com> (raw)
DG1 at a state where we can safely remove require_force_probe.
Signed-off-by: Anusha Srivatsa <anusha.srivatsa@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 f449c454b6f8..cafc569fdf66 100644
--- a/drivers/gpu/drm/i915/i915_pci.c
+++ b/drivers/gpu/drm/i915/i915_pci.c
@@ -909,7 +909,6 @@ static const struct intel_device_info dg1_info = {
.graphics.rel = 10,
PLATFORM(INTEL_DG1),
.display.pipe_mask = BIT(PIPE_A) | BIT(PIPE_B) | BIT(PIPE_C) | BIT(PIPE_D),
- .require_force_probe = 1,
.platform_engine_mask =
BIT(RCS0) | BIT(BCS0) | BIT(VECS0) |
BIT(VCS0) | BIT(VCS2),
--
2.25.1
next reply other threads:[~2022-02-22 18:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 18:19 Anusha Srivatsa [this message]
2022-02-22 19:47 ` [Intel-gfx] [PATCH] drm/i915/dg1: Remove require_force_probe protection Lucas De Marchi
2022-02-23 4:12 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-02-24 2:50 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/dg1: Remove require_force_probe protection (rev2) Patchwork
2022-02-24 14:35 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2022-10-21 5:47 [Intel-gfx] [PATCH] drm/i915/dg1: Remove require_force_probe protection Chaitanya Kumar Borah
2022-11-23 16:51 ` 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=20220222181937.592346-1-anusha.srivatsa@intel.com \
--to=anusha.srivatsa@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