From: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH 1/2] drm/i915/display: Drop check for doublescan mode in modevalid
Date: Mon, 17 Oct 2022 20:00:37 +0530 [thread overview]
Message-ID: <20221017143038.1748319-2-ankit.k.nautiyal@intel.com> (raw)
In-Reply-To: <20221017143038.1748319-1-ankit.k.nautiyal@intel.com>
Since the DP/HDMI connector do not set connector->doublescan_allowed,
the doublescan modes will get automatically filtered during
drm_helper_probe_single_connector_modes().
Therefore check for double scan modes is not required and is dropped
from modevalid functions for both DP and HDMI.
Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
---
drivers/gpu/drm/i915/display/intel_dp.c | 3 ---
drivers/gpu/drm/i915/display/intel_hdmi.c | 3 ---
2 files changed, 6 deletions(-)
diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
index a060903891b2..1f83ddf13928 100644
--- a/drivers/gpu/drm/i915/display/intel_dp.c
+++ b/drivers/gpu/drm/i915/display/intel_dp.c
@@ -973,9 +973,6 @@ intel_dp_mode_valid(struct drm_connector *_connector,
enum drm_mode_status status;
bool dsc = false, bigjoiner = false;
- if (mode->flags & DRM_MODE_FLAG_DBLSCAN)
- return MODE_NO_DBLESCAN;
-
if (mode->flags & DRM_MODE_FLAG_DBLCLK)
return MODE_H_ILLEGAL;
diff --git a/drivers/gpu/drm/i915/display/intel_hdmi.c b/drivers/gpu/drm/i915/display/intel_hdmi.c
index 93519fb23d9d..e21deb6ef7fa 100644
--- a/drivers/gpu/drm/i915/display/intel_hdmi.c
+++ b/drivers/gpu/drm/i915/display/intel_hdmi.c
@@ -1987,9 +1987,6 @@ intel_hdmi_mode_valid(struct drm_connector *connector,
bool has_hdmi_sink = intel_has_hdmi_sink(hdmi, connector->state);
bool ycbcr_420_only;
- if (mode->flags & DRM_MODE_FLAG_DBLSCAN)
- return MODE_NO_DBLESCAN;
-
if ((mode->flags & DRM_MODE_FLAG_3D_MASK) == DRM_MODE_FLAG_3D_FRAME_PACKING)
clock *= 2;
--
2.25.1
next prev parent reply other threads:[~2022-10-17 14:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 14:30 [Intel-gfx] [PATCH 0/2] Defeature Interlace modes for Display >= 12 Ankit Nautiyal
2022-10-17 14:30 ` Ankit Nautiyal [this message]
2023-01-05 11:47 ` [Intel-gfx] [PATCH 1/2] drm/i915/display: Drop check for doublescan mode in modevalid Jani Nikula
2022-10-17 14:30 ` [Intel-gfx] [PATCH 2/2] drm/i915/display: Prune Interlace modes for Display >=12 Ankit Nautiyal
2023-01-05 11:44 ` Jani Nikula
2023-01-05 12:41 ` [Intel-gfx] [PATCH v3 " Ankit Nautiyal
2023-01-05 12:49 ` Jani Nikula
2022-10-17 15:01 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Defeature Interlace modes for Display >= 12 Patchwork
2022-10-17 21:22 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-10-19 7:12 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Defeature Interlace modes for Display >= 12 (rev2) Patchwork
2022-10-19 14:10 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-01-05 17:03 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for Defeature Interlace modes for Display >= 12 (rev3) Patchwork
2023-01-06 4:03 ` Nautiyal, Ankit K
2023-01-06 15:36 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Defeature Interlace modes for Display >= 12 (rev4) Patchwork
2023-01-06 18:17 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-01-12 7:44 ` [Intel-gfx] [PATCH 0/2] Defeature Interlace modes for Display >= 12 Shankar, Uma
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=20221017143038.1748319-2-ankit.k.nautiyal@intel.com \
--to=ankit.k.nautiyal@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