public inbox for intel-xe@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v6] drm/i915/display: change pipe allocation order for discrete platforms
Date: Wed, 15 Apr 2026 13:57:29 +0300	[thread overview]
Message-ID: <c510d0d848ca57637120803f256870d29dee5482@intel.com> (raw)
In-Reply-To: <ad9aZ9oYYLWLbni1@intel.com>

On Wed, 15 Apr 2026, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Mon, Apr 13, 2026 at 11:16:09AM +0300, Jani Nikula wrote:
>> When big joiner is enabled, it reserves the adjacent pipe as the
>> secondary pipe. This happens without the user space knowing, and
>> subsequent attempts at using the CRTC with that pipe will fail. If the
>> user space does not have a coping mechanism, i.e. trying another CRTC,
>> this leads to a black screen.
>> 
>> Try to reduce the impact of the problem on discrete platforms by mapping
>> the CRTCs to pipes in order A, C, B, and D. If the user space reserves
>> CRTCs in order, this should trick it to using pipes that are more likely
>> to be available for and after joining.
>> 
>> Limit this to discrete platforms, which have four pipes, and no eDP, a
>> combination that should benefit the most with least drawbacks.
>> 
>> Cc: Ville Syrjala <ville.syrjala@linux.intel.com>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> Should be fine with the other stuff I posted earlier:
> https://lore.kernel.org/intel-gfx/20260408155744.13326-1-ville.syrjala@linux.intel.com/
>
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

Thanks, pushed top topic/pipe-reorder, which already has the commits you
refer to.

BR,
Jani.

>
>> 
>> ---
>> 
>> v2: Also remove WARN_ON()
>> 
>> v3: Limit to discrete
>> 
>> v4: Revamp
>> 
>> v5: Don't screw up the loop variable, dummy
>> 
>> v6: Rebase, drop FIXME comment
>> ---
>>  drivers/gpu/drm/i915/display/intel_crtc.c | 29 ++++++++++++++++++++---
>>  1 file changed, 26 insertions(+), 3 deletions(-)
>> 
>> diff --git a/drivers/gpu/drm/i915/display/intel_crtc.c b/drivers/gpu/drm/i915/display/intel_crtc.c
>> index c88a6810c49f..03de219f7a64 100644
>> --- a/drivers/gpu/drm/i915/display/intel_crtc.c
>> +++ b/drivers/gpu/drm/i915/display/intel_crtc.c
>> @@ -411,8 +411,6 @@ static int __intel_crtc_init(struct intel_display *display, enum pipe pipe)
>>  
>>  	cpu_latency_qos_add_request(&crtc->vblank_pm_qos, PM_QOS_DEFAULT_VALUE);
>>  
>> -	drm_WARN_ON(display->drm, drm_crtc_index(&crtc->base) != crtc->pipe);
>> -
>>  	if (HAS_CASF(display) && crtc->num_scalers >= 2)
>>  		drm_crtc_create_sharpness_strength_property(&crtc->base);
>>  
>> @@ -426,6 +424,31 @@ static int __intel_crtc_init(struct intel_display *display, enum pipe pipe)
>>  	return ret;
>>  }
>>  
>> +#define HAS_PIPE(display, pipe) (DISPLAY_RUNTIME_INFO(display)->pipe_mask & BIT(pipe))
>> +
>> +/*
>> + * Expose the pipes in order A, C, B, D on discrete platforms to trick user
>> + * space into using pipes that are more likely to be available for both a) user
>> + * space if pipe B has been reserved for the joiner, and b) the joiner if pipe A
>> + * doesn't need the joiner.
>> + *
>> + * Swap pipes B and C only if both are available i.e. not fused off.
>> + */
>> +static enum pipe reorder_pipe(struct intel_display *display, enum pipe pipe)
>> +{
>> +	if (!display->platform.dgfx || !HAS_PIPE(display, PIPE_B) || !HAS_PIPE(display, PIPE_C))
>> +		return pipe;
>> +
>> +	switch (pipe) {
>> +	case PIPE_B:
>> +		return PIPE_C;
>> +	case PIPE_C:
>> +		return PIPE_B;
>> +	default:
>> +		return pipe;
>> +	}
>> +}
>> +
>>  int intel_crtc_init(struct intel_display *display)
>>  {
>>  	enum pipe pipe;
>> @@ -435,7 +458,7 @@ int intel_crtc_init(struct intel_display *display)
>>  		    INTEL_NUM_PIPES(display), str_plural(INTEL_NUM_PIPES(display)));
>>  
>>  	for_each_pipe(display, pipe) {
>> -		ret = __intel_crtc_init(display, pipe);
>> +		ret = __intel_crtc_init(display, reorder_pipe(display, pipe));
>>  		if (ret)
>>  			return ret;
>>  	}
>> -- 
>> 2.47.3

-- 
Jani Nikula, Intel

      reply	other threads:[~2026-04-15 10:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-13  8:16 [PATCH v6] drm/i915/display: change pipe allocation order for discrete platforms Jani Nikula
2026-04-14 22:28 ` ✓ CI.KUnit: success for drm/i915/display: change pipe allocation order for discrete platforms (rev6) Patchwork
2026-04-14 23:33 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-15  0:11 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-04-15  9:29 ` [PATCH v6] drm/i915/display: change pipe allocation order for discrete platforms Ville Syrjälä
2026-04-15 10:57   ` Jani Nikula [this message]

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=c510d0d848ca57637120803f256870d29dee5482@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=ville.syrjala@linux.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