From: Suraj Kandpal <suraj.kandpal@intel.com>
To: intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Cc: ankit.k.nautiyal@intel.com, matthew.d.roper@intel.com,
Suraj Kandpal <suraj.kandpal@intel.com>
Subject: [PATCH 3/3] drm/i914/xe3lpd: Increase bigjoiner limitations
Date: Mon, 28 Oct 2024 13:13:33 +0530 [thread overview]
Message-ID: <20241028074333.182041-4-suraj.kandpal@intel.com> (raw)
In-Reply-To: <20241028074333.182041-1-suraj.kandpal@intel.com>
With 6k resolution support for a single crtc being added
bigjoiner will only come into picture when hdisplay > 6144
Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
Reviewed-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
---
drivers/gpu/drm/i915/display/intel_dp.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
index 7e29619ba040..9dd4610c749a 100644
--- a/drivers/gpu/drm/i915/display/intel_dp.c
+++ b/drivers/gpu/drm/i915/display/intel_dp.c
@@ -1315,14 +1315,17 @@ bool intel_dp_needs_joiner(struct intel_dp *intel_dp,
int num_joined_pipes)
{
struct drm_i915_private *i915 = dp_to_i915(intel_dp);
+ int hdisplay_limit;
if (!intel_dp_has_joiner(intel_dp))
return false;
num_joined_pipes /= 2;
+ hdisplay_limit = DISPLAY_VER(i915) >= 30 ? 6144 : 5120;
+
return clock > num_joined_pipes * i915->display.cdclk.max_dotclk_freq ||
- hdisplay > num_joined_pipes * 5120;
+ hdisplay > num_joined_pipes * hdisplay_limit;
}
int intel_dp_num_joined_pipes(struct intel_dp *intel_dp,
--
2.34.1
next prev parent reply other threads:[~2024-10-28 7:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 7:43 [PATCH 0/5] Add 6k resolution support for a single CRTC Suraj Kandpal
2024-10-28 7:43 ` [PATCH 1/3] drm/i915/xe3lpd: Increase resolution for plane to support 6k Suraj Kandpal
2024-10-28 7:43 ` [PATCH 2/3] drm/i915/psr: Change psr size limits check Suraj Kandpal
2024-10-28 12:44 ` Nautiyal, Ankit K
2024-10-28 12:54 ` Nautiyal, Ankit K
2024-10-28 13:00 ` Suraj Kandpal
2024-10-28 21:11 ` Matt Roper
2024-10-28 7:43 ` Suraj Kandpal [this message]
2024-10-28 15:00 ` ✓ CI.Patch_applied: success for Add 6k resolution support for a single CRTC (rev5) Patchwork
2024-10-28 15:00 ` ✓ CI.checkpatch: " Patchwork
2024-10-28 15:02 ` ✓ CI.KUnit: " Patchwork
2024-10-28 15:20 ` ✓ CI.Build: " Patchwork
2024-10-28 15:23 ` ✓ CI.Hooks: " Patchwork
2024-10-28 15:24 ` ✗ CI.checksparse: warning " Patchwork
2024-10-28 16:09 ` ✓ CI.BAT: success " Patchwork
2024-10-28 17:19 ` ✗ CI.FULL: failure " Patchwork
2024-10-29 11:03 ` ✗ Fi.CI.SPARSE: warning " Patchwork
2024-10-29 11:37 ` ✓ Fi.CI.BAT: success " Patchwork
2024-10-29 11:51 ` ✗ CI.FULL: failure " Patchwork
2024-10-29 13:36 ` ✗ Fi.CI.IGT: " Patchwork
2024-10-30 19:31 ` 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=20241028074333.182041-4-suraj.kandpal@intel.com \
--to=suraj.kandpal@intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.d.roper@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.