Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 2/4] drm/i915/mst: Disable transcoder before deleting the payload
Date: Wed, 1 Nov 2023 12:27:03 +0200	[thread overview]
Message-ID: <ZUIn90ljTBuekk-5@intel.com> (raw)
In-Reply-To: <20231018154123.5479-3-ville.syrjala@linux.intel.com>

On Wed, Oct 18, 2023 at 06:41:21PM +0300, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> 
> Bspec tells us that we should disable the transcoder before
> deleting the payload. Looks like this has been reversed since
> MST support was added.

I suppose this shouldn't matter in practice since the downstream
device shouldn't really do anything with the new payload until
we send the ACT. But I see no compelling reason to deviate from
the bspec sequence regardless.

> 
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_dp_mst.c | 8 ++------
>  1 file changed, 2 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_dp_mst.c b/drivers/gpu/drm/i915/display/intel_dp_mst.c
> index 7b4628f4f124..57eb581b8a50 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp_mst.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp_mst.c
> @@ -587,10 +587,6 @@ static void intel_mst_disable_dp(struct intel_atomic_state *state,
>  	struct intel_dp *intel_dp = &dig_port->dp;
>  	struct intel_connector *connector =
>  		to_intel_connector(old_conn_state->connector);
> -	struct drm_dp_mst_topology_state *new_mst_state =
> -		drm_atomic_get_new_mst_topology_state(&state->base, &intel_dp->mst_mgr);
> -	struct drm_dp_mst_atomic_payload *new_payload =
> -		drm_atomic_get_mst_payload_state(new_mst_state, connector->port);
>  	struct drm_i915_private *i915 = to_i915(connector->base.dev);
>  
>  	drm_dbg_kms(&i915->drm, "active links %d\n",
> @@ -598,8 +594,6 @@ static void intel_mst_disable_dp(struct intel_atomic_state *state,
>  
>  	intel_hdcp_disable(intel_mst->connector);
>  
> -	drm_dp_remove_payload_part1(&intel_dp->mst_mgr, new_mst_state, new_payload);
> -
>  	intel_audio_codec_disable(encoder, old_crtc_state, old_conn_state);
>  }
>  
> @@ -634,6 +628,8 @@ static void intel_mst_post_disable_dp(struct intel_atomic_state *state,
>  
>  	intel_disable_transcoder(old_crtc_state);
>  
> +	drm_dp_remove_payload_part1(&intel_dp->mst_mgr, new_mst_state, new_payload);
> +
>  	clear_act_sent(encoder, old_crtc_state);
>  
>  	intel_de_rmw(dev_priv, TRANS_DDI_FUNC_CTL(old_crtc_state->cpu_transcoder),
> -- 
> 2.41.0

-- 
Ville Syrjälä
Intel

  parent reply	other threads:[~2023-11-01 10:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-18 15:41 [Intel-gfx] [PATCH 0/4] drm/i915/mst: MST modeset sequence fixes Ville Syrjala
2023-10-18 15:41 ` [Intel-gfx] [PATCH 1/4] drm/i915/mst: Swap TRANSCONF vs. FECSTALL_DIS_DPTSTREAM_DPTTG disable Ville Syrjala
2023-10-30 12:38   ` Jani Nikula
2023-10-18 15:41 ` [Intel-gfx] [PATCH 2/4] drm/i915/mst: Disable transcoder before deleting the payload Ville Syrjala
2023-10-30 12:42   ` Jani Nikula
2023-11-01 10:27   ` Ville Syrjälä [this message]
2023-10-18 15:41 ` [Intel-gfx] [PATCH 3/4] drm/i915/mst: Clear ACT just before triggering payload allocation Ville Syrjala
2023-10-30 12:44   ` Jani Nikula
2023-10-30 12:44   ` Jani Nikula
2023-10-18 15:41 ` [Intel-gfx] [PATCH 4/4] drm/i915/mst: Always write CHICKEN_TRANS Ville Syrjala
2023-10-30 12:45   ` Jani Nikula
2023-10-18 23:34 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/mst: MST modeset sequence fixes Patchwork
2023-10-18 23:42 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-10-24 13:15 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/mst: MST modeset sequence fixes (rev2) Patchwork
2023-10-24 13:25 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-10-24 22:57 ` [Intel-gfx] ✗ Fi.CI.IGT: 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=ZUIn90ljTBuekk-5@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /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