public inbox for intel-xe@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Michał Grzelak" <michal.grzelak@intel.com>,
	"Imre Deak" <imre.deak@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
	"Uma Shankar" <uma.shankar@intel.com>,
	"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH] drm/i915/dp_tunnel: Fix error handling when clearing stream BW in atomic state
Date: Fri, 20 Mar 2026 13:19:32 +0200	[thread overview]
Message-ID: <99351a6c5d3da05614e3132f2dd562a54df5e1c4@intel.com> (raw)
In-Reply-To: <bbaf3e50-4660-877f-579d-82fa406e077e@intel.com>

On Fri, 20 Mar 2026, Michał Grzelak <michal.grzelak@intel.com> wrote:
> On Fri, 20 Mar 2026, Imre Deak wrote:
>> Clearing the DP tunnel stream BW in the atomic state involves getting
>> the tunnel group state, which can fail. Handle the error accordingly.
>>
>> This fixes at least one issue where drm_dp_tunnel_atomic_set_stream_bw()
>> failed to get the tunnel group state returning -EDEADLK, which wasn't
>> handled. This lead to the ctx->contended warn later in modeset_lock()
>> while taking a WW mutex for another object in the same atomic state, and
>> thus within the same already contended WW context.
>>
>> Moving intel_crtc_state_alloc() later would avoid freeing saved_state on
>> the error path; this stable patch leaves that simplification for a
>> follow-up.
>>
>> Cc: Uma Shankar <uma.shankar@intel.com>
>> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> Cc: <stable@vger.kernel.org> # v6.9+
>> Fixes: a4efae87ecb2 ("drm/i915/dp: Compute DP tunnel BW during encoder state computation")
>> Signed-off-by: Imre Deak <imre.deak@intel.com>
>> ---
>> drivers/gpu/drm/i915/display/intel_display.c  |  8 +++++++-
>> .../gpu/drm/i915/display/intel_dp_tunnel.c    | 20 +++++++++++++------
>> .../gpu/drm/i915/display/intel_dp_tunnel.h    | 11 ++++++----
>> 3 files changed, 28 insertions(+), 11 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c
>> index ee501009a251f..882db77c0bbcd 100644
>> --- a/drivers/gpu/drm/i915/display/intel_display.c
>> +++ b/drivers/gpu/drm/i915/display/intel_display.c
>> @@ -4640,6 +4640,7 @@ intel_crtc_prepare_cleared_state(struct intel_atomic_state *state,
>> 	struct intel_crtc_state *crtc_state =
>> 		intel_atomic_get_new_crtc_state(state, crtc);
>> 	struct intel_crtc_state *saved_state;
>> +	int err;
>>
>> 	saved_state = intel_crtc_state_alloc(crtc);
>> 	if (!saved_state)
>> @@ -4648,7 +4649,12 @@ intel_crtc_prepare_cleared_state(struct intel_atomic_state *state,
>> 	/* free the old crtc_state->hw members */
>> 	intel_crtc_free_hw_state(crtc_state);
>>
>> -	intel_dp_tunnel_atomic_clear_stream_bw(state, crtc_state);
>> +	err = intel_dp_tunnel_atomic_clear_stream_bw(state, crtc_state);
>> +	if (err) {
>> +		kfree(saved_state);
>> +
>
> I am unsure if the blank line above is neccessary, but I might be also
> missing style guidelines. Otherwise looks good to me.

It's a common convention to have a blank line before return.

BR,
Jani.

>
> Reviewed-by: Michał Grzelak <michal.grzelak@intel.com>
>
> BR,
> Michał
>
>> +		return err;
>> +	}
>>
>> 	/* FIXME: before the switch to atomic started, a new pipe_config was
>> 	 * kzalloc'd. Code that depends on any field being zero should be
>> diff --git a/drivers/gpu/drm/i915/display/intel_dp_tunnel.c b/drivers/gpu/drm/i915/display/intel_dp_tunnel.c
>> index 1fd1ac8d556d8..7363c98172971 100644
>> --- a/drivers/gpu/drm/i915/display/intel_dp_tunnel.c
>> +++ b/drivers/gpu/drm/i915/display/intel_dp_tunnel.c
>> @@ -659,19 +659,27 @@ int intel_dp_tunnel_atomic_compute_stream_bw(struct intel_atomic_state *state,
>>  *
>>  * Clear any DP tunnel stream BW requirement set by
>>  * intel_dp_tunnel_atomic_compute_stream_bw().
>> + *
>> + * Returns 0 in case of success, a negative error code otherwise.
>>  */
>> -void intel_dp_tunnel_atomic_clear_stream_bw(struct intel_atomic_state *state,
>> -					    struct intel_crtc_state *crtc_state)
>> +int intel_dp_tunnel_atomic_clear_stream_bw(struct intel_atomic_state *state,
>> +					   struct intel_crtc_state *crtc_state)
>> {
>> 	struct intel_crtc *crtc = to_intel_crtc(crtc_state->uapi.crtc);
>> +	int err;
>>
>> 	if (!crtc_state->dp_tunnel_ref.tunnel)
>> -		return;
>> +		return 0;
>> +
>> +	err = drm_dp_tunnel_atomic_set_stream_bw(&state->base,
>> +						 crtc_state->dp_tunnel_ref.tunnel,
>> +						 crtc->pipe, 0);
>> +	if (err)
>> +		return err;
>>
>> -	drm_dp_tunnel_atomic_set_stream_bw(&state->base,
>> -					   crtc_state->dp_tunnel_ref.tunnel,
>> -					   crtc->pipe, 0);
>> 	drm_dp_tunnel_ref_put(&crtc_state->dp_tunnel_ref);
>> +
>> +	return 0;
>> }
>>
>> /**
>> diff --git a/drivers/gpu/drm/i915/display/intel_dp_tunnel.h b/drivers/gpu/drm/i915/display/intel_dp_tunnel.h
>> index 7f0f720e8dcad..10ab9eebcef69 100644
>> --- a/drivers/gpu/drm/i915/display/intel_dp_tunnel.h
>> +++ b/drivers/gpu/drm/i915/display/intel_dp_tunnel.h
>> @@ -40,8 +40,8 @@ int intel_dp_tunnel_atomic_compute_stream_bw(struct intel_atomic_state *state,
>> 					     struct intel_dp *intel_dp,
>> 					     const struct intel_connector *connector,
>> 					     struct intel_crtc_state *crtc_state);
>> -void intel_dp_tunnel_atomic_clear_stream_bw(struct intel_atomic_state *state,
>> -					    struct intel_crtc_state *crtc_state);
>> +int intel_dp_tunnel_atomic_clear_stream_bw(struct intel_atomic_state *state,
>> +					   struct intel_crtc_state *crtc_state);
>>
>> int intel_dp_tunnel_atomic_add_state_for_crtc(struct intel_atomic_state *state,
>> 					      struct intel_crtc *crtc);
>> @@ -88,9 +88,12 @@ intel_dp_tunnel_atomic_compute_stream_bw(struct intel_atomic_state *state,
>> 	return 0;
>> }
>>
>> -static inline void
>> +static inline int
>> intel_dp_tunnel_atomic_clear_stream_bw(struct intel_atomic_state *state,
>> -				       struct intel_crtc_state *crtc_state) {}
>> +				       struct intel_crtc_state *crtc_state)
>> +{
>> +	return 0;
>> +}
>>
>> static inline int
>> intel_dp_tunnel_atomic_add_state_for_crtc(struct intel_atomic_state *state,
>> -- 
>> 2.49.1
>>
>>

-- 
Jani Nikula, Intel

  parent reply	other threads:[~2026-03-20 11:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-20  9:29 [PATCH] drm/i915/dp_tunnel: Fix error handling when clearing stream BW in atomic state Imre Deak
2026-03-20  9:46 ` ✓ CI.KUnit: success for " Patchwork
2026-03-20 10:20 ` [PATCH] " Michał Grzelak
2026-03-20 10:38   ` Imre Deak
2026-03-20 11:19   ` Jani Nikula [this message]
2026-03-20 10:33 ` ✓ Xe.CI.BAT: success for " Patchwork
2026-03-20 11:42 ` [PATCH] " Shankar, Uma
2026-03-20 14:55   ` Imre Deak
2026-03-20 22:17     ` Shankar, Uma
2026-03-21  7:09 ` ✗ Xe.CI.FULL: failure for " 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=99351a6c5d3da05614e3132f2dd562a54df5e1c4@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=imre.deak@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=michal.grzelak@intel.com \
    --cc=stable@vger.kernel.org \
    --cc=uma.shankar@intel.com \
    --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