public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [RFC 4/7] drm/i915/dp: Allow big joiner modes in intel_dp_mode_valid()
Date: Tue,  2 Jul 2019 21:42:02 +0200	[thread overview]
Message-ID: <20190702194205.13366-5-maarten.lankhorst@linux.intel.com> (raw)
In-Reply-To: <20190702194205.13366-1-maarten.lankhorst@linux.intel.com>

Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
---
 drivers/gpu/drm/i915/display/intel_dp.c | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
index d5c56ea079a4..b41ff88d3258 100644
--- a/drivers/gpu/drm/i915/display/intel_dp.c
+++ b/drivers/gpu/drm/i915/display/intel_dp.c
@@ -506,6 +506,7 @@ intel_dp_mode_valid(struct drm_connector *connector,
 	int max_dotclk;
 	u16 dsc_max_output_bpp = 0;
 	u8 dsc_slice_count = 0;
+	bool dsc;
 
 	if (mode->flags & DRM_MODE_FLAG_DBLSCAN)
 		return MODE_NO_DBLESCAN;
@@ -553,8 +554,13 @@ intel_dp_mode_valid(struct drm_connector *connector,
 		}
 	}
 
-	if ((mode_rate > max_rate && !(dsc_max_output_bpp && dsc_slice_count)) ||
-	    target_clock > max_dotclk)
+	dsc = dsc_max_output_bpp && dsc_slice_count;
+
+	/* Gen11 has big joiner for handling this */
+	if (dsc && dsc_slice_count >= 2 && INTEL_GEN(dev_priv) >= 11)
+		max_dotclk *= 2;
+
+	if ((mode_rate > max_rate && !dsc) || target_clock > max_dotclk)
 		return MODE_CLOCK_HIGH;
 
 	if (mode->clock < 10000)
-- 
2.20.1

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2019-07-02 19:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-02 19:41 [RFC 0/7] Bigjoiner atomic preparations Maarten Lankhorst
2019-07-02 19:41 ` [RFC 1/7] drm/i915: Prepare to split crtc state in uapi and hw state Maarten Lankhorst
2019-07-02 19:42 ` [RFC 2/7] drm/i915: Handle a few more cases for hw/sw split Maarten Lankhorst
2019-07-02 19:42 ` [RFC 3/7] drm/i915: Complete sw/hw split Maarten Lankhorst
2019-07-02 19:42 ` Maarten Lankhorst [this message]
2019-07-03  0:13   ` [RFC 4/7] drm/i915/dp: Allow big joiner modes in intel_dp_mode_valid() Manasi Navare
2019-07-02 19:42 ` [RFC 5/7] drm/i915/dp: Validate modes that can only be handled in a bigjoiner configuration Maarten Lankhorst
2019-07-02 19:42 ` [RFC 6/7] drm/i915: Try to make bigjoiner work in atomic check Maarten Lankhorst
2019-07-03  0:32   ` Manasi Navare
2019-07-03  8:02     ` Maarten Lankhorst
2019-07-02 19:42 ` [RFC 7/7] drm/i915: Allow vdsc functions to be called without encoder Maarten Lankhorst
2019-07-10 22:35   ` Manasi Navare
2019-07-30  9:08     ` Maarten Lankhorst
2019-08-21 19:54       ` Manasi Navare
2019-07-02 21:30 ` ✗ Fi.CI.CHECKPATCH: warning for Bigjoiner atomic preparations Patchwork
2019-07-02 21:33 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-07-02 21:59 ` ✓ Fi.CI.BAT: success " Patchwork
2019-07-03 22:04 ` ✓ Fi.CI.IGT: " Patchwork

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=20190702194205.13366-5-maarten.lankhorst@linux.intel.com \
    --to=maarten.lankhorst@linux.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