Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: Jani Nikula <jani.nikula@intel.com>,
	<intel-gfx@lists.freedesktop.org>,
	<intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 2/4] drm/i915/dp: Limit for_each_joiner_candidate() on joiner pipes available
Date: Mon, 10 Aug 2026 17:06:44 +0530	[thread overview]
Message-ID: <37c48d39-acbb-473f-aee8-bdf508483357@intel.com> (raw)
In-Reply-To: <efc330687f8299e5725564c3ed90d5d8e6aa0eb2.1786105831.git.jani.nikula@intel.com>


On 8/7/2026 6:04 PM, Jani Nikula wrote:
> Make intel_dp_can_join(), and subsequently
> intel_dp_joiner_candidate_valid() and for_each_joiner_candidate() more
> strict about pipes actually available for joining by using
> intel_joiner_valid_primary_pipe_mask().
>
> This rejects some invalid combos early for both mode enumeration and
> compute config.
>
> Cc: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>

LGTM.

Reviewed-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>


> ---
>   drivers/gpu/drm/i915/display/intel_dp.c | 12 +-----------
>   1 file changed, 1 insertion(+), 11 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
> index 437b9e7bb864..e1604bc895e5 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> @@ -1274,17 +1274,7 @@ bool intel_dp_can_join(struct intel_dp *intel_dp,
>   	if (num_joined_pipes > 1 && !intel_dp_has_joiner(intel_dp))
>   		return false;
>   
> -	switch (num_joined_pipes) {
> -	case 1:
> -		return true;
> -	case 2:
> -		return HAS_BIGJOINER(display) ||
> -		       HAS_UNCOMPRESSED_JOINER(display);
> -	case 4:
> -		return HAS_ULTRAJOINER(display);
> -	default:
> -		return false;
> -	}
> +	return intel_joiner_valid_primary_pipe_mask(display, num_joined_pipes);
>   }
>   
>   bool intel_dp_dotclk_valid(struct intel_display *display,

  reply	other threads:[~2026-08-10 11:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-07 12:34 [PATCH 0/4] drm/i915/display: Limit invalid joiner combinations harder Jani Nikula
2026-08-07 12:34 ` [PATCH 1/4] drm/i915/display: Limit max joined dotclock on joiner pipes available Jani Nikula
2026-08-10 11:17   ` Nautiyal, Ankit K
2026-08-11 12:47     ` Jani Nikula
2026-08-07 12:34 ` [PATCH 2/4] drm/i915/dp: Limit for_each_joiner_candidate() " Jani Nikula
2026-08-10 11:36   ` Nautiyal, Ankit K [this message]
2026-08-07 12:34 ` [PATCH 3/4] drm/i915/dp: Limit compute config joining to pipes that can actually join Jani Nikula
2026-08-10 11:41   ` Nautiyal, Ankit K
2026-08-07 12:34 ` [PATCH 4/4] drm/i915/debugfs: Reject invalid force_joined_pipes harder Jani Nikula
2026-08-10 11:43   ` Nautiyal, Ankit K
2026-08-07 13:00 ` ✗ CI.checkpatch: warning for drm/i915/display: Limit invalid joiner combinations harder Patchwork
2026-08-07 13:01 ` ✓ CI.KUnit: success " Patchwork
2026-08-07 13:44 ` ✓ Xe.CI.BAT: " Patchwork
2026-08-07 22:40 ` ✗ Xe.CI.FULL: failure " 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=37c48d39-acbb-473f-aee8-bdf508483357@intel.com \
    --to=ankit.k.nautiyal@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@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