From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>,
<intel-xe@lists.freedesktop.org>,
<intel-gfx@lists.freedesktop.org>
Cc: <matthew.d.roper@intel.com>
Subject: Re: [PATCH 3/4] drm/i914/xe3lpd: Increase bigjoiner limitations
Date: Thu, 24 Oct 2024 17:21:57 +0530 [thread overview]
Message-ID: <8542be0e-2079-4a20-8b1f-2e7ce6ba7602@intel.com> (raw)
In-Reply-To: <20241024035552.94363-4-suraj.kandpal@intel.com>
On 10/24/2024 9:25 AM, Suraj Kandpal wrote:
> 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 fbb096be02ad..e0baad468d76 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> @@ -1313,14 +1313,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,
next prev parent reply other threads:[~2024-10-24 11:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 3:55 [PATCH 0/4] Add 6k resolution support for a single CRTC Suraj Kandpal
2024-10-24 3:55 ` [PATCH 1/4] drm/i915/xe3lpd: Increase resolution for plane to support 6k Suraj Kandpal
2024-10-24 11:46 ` Nautiyal, Ankit K
2024-10-24 19:48 ` Matt Roper
2024-10-25 4:05 ` Nautiyal, Ankit K
2024-10-24 3:55 ` [PATCH 2/4] drm/i915/xe3lpd: Increase max_h max_v for PSR Suraj Kandpal
2024-10-24 13:04 ` Nautiyal, Ankit K
2024-10-24 19:59 ` Matt Roper
2024-10-24 3:55 ` [PATCH 3/4] drm/i914/xe3lpd: Increase bigjoiner limitations Suraj Kandpal
2024-10-24 11:51 ` Nautiyal, Ankit K [this message]
2024-10-24 3:55 ` [PATCH 4/4] drm/i915/xe3lpd: Prune modes for YUV420 Suraj Kandpal
2024-10-24 12:20 ` Nautiyal, Ankit K
2024-10-24 20:27 ` ✓ CI.Patch_applied: success for Add 6k resolution support for a single CRTC (rev2) Patchwork
2024-10-24 20:27 ` ✓ CI.checkpatch: " Patchwork
2024-10-24 20:28 ` ✓ CI.KUnit: " Patchwork
2024-10-24 20:40 ` ✓ CI.Build: " Patchwork
2024-10-24 20:42 ` ✓ CI.Hooks: " Patchwork
2024-10-24 20:44 ` ✗ CI.checksparse: warning " Patchwork
2024-10-24 21:16 ` ✗ CI.BAT: failure " Patchwork
2024-10-26 3:25 ` ✗ CI.FULL: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2024-10-15 6:10 [PATCH 0/4] Add 6k resolution support for a single CRTC Suraj Kandpal
2024-10-15 6:10 ` [PATCH 3/4] drm/i914/xe3lpd: Increase bigjoiner limitations Suraj Kandpal
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=8542be0e-2079-4a20-8b1f-2e7ce6ba7602@intel.com \
--to=ankit.k.nautiyal@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.d.roper@intel.com \
--cc=suraj.kandpal@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox