Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: Imre Deak <imre.deak@intel.com>, <intel-gfx@lists.freedesktop.org>
Cc: Sandeep K Lakkakula <sandeep.k.lakkakula@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/tgl+: Fix HDMI transcoder clock vs. DDI BUF disabling order
Date: Tue, 12 Jul 2022 11:05:13 +0530	[thread overview]
Message-ID: <ed0fcb48-c23e-4faa-fbf7-7cdcea4ae968@intel.com> (raw)
In-Reply-To: <20220617112807.1586621-1-imre.deak@intel.com>

Change is according to the specs. I see similar thing for DP as well, 
and its already taken care in disable DP path,

seems like it was missing only for HDMI.

LGTM.

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

On 6/17/2022 4:58 PM, Imre Deak wrote:
> Starting with TGL the disabling order of HDMI transcoder clock vs. DDI
> BUF has swapped, fix this. There hasn't been any issues seen related to
> this, but let's follow the spec.
>
> Reported-by: Sandeep K Lakkakula <sandeep.k.lakkakula@intel.com>
> Signed-off-by: Imre Deak <imre.deak@intel.com>
> ---
>   drivers/gpu/drm/i915/display/intel_ddi.c | 6 +++++-
>   1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_ddi.c b/drivers/gpu/drm/i915/display/intel_ddi.c
> index 272e1bf6006be..4b874c31398a2 100644
> --- a/drivers/gpu/drm/i915/display/intel_ddi.c
> +++ b/drivers/gpu/drm/i915/display/intel_ddi.c
> @@ -2691,10 +2691,14 @@ static void intel_ddi_post_disable_hdmi(struct intel_atomic_state *state,
>   	dig_port->set_infoframes(encoder, false,
>   				 old_crtc_state, old_conn_state);
>   
> -	intel_ddi_disable_pipe_clock(old_crtc_state);
> +	if (DISPLAY_VER(dev_priv) < 12)
> +		intel_ddi_disable_pipe_clock(old_crtc_state);
>   
>   	intel_disable_ddi_buf(encoder, old_crtc_state);
>   
> +	if (DISPLAY_VER(dev_priv) >= 12)
> +		intel_ddi_disable_pipe_clock(old_crtc_state);
> +
>   	intel_display_power_put(dev_priv,
>   				dig_port->ddi_io_power_domain,
>   				fetch_and_zero(&dig_port->ddi_io_wakeref));

      parent reply	other threads:[~2022-07-12  5:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17 11:28 [Intel-gfx] [PATCH] drm/i915/tgl+: Fix HDMI transcoder clock vs. DDI BUF disabling order Imre Deak
2022-06-17 15:19 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-06-18  0:50 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-07-18 12:21   ` Imre Deak
2022-07-19 15:07     ` Vudum, Lakshminarayana
2022-07-12  5:35 ` Nautiyal, Ankit K [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=ed0fcb48-c23e-4faa-fbf7-7cdcea4ae968@intel.com \
    --to=ankit.k.nautiyal@intel.com \
    --cc=imre.deak@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=sandeep.k.lakkakula@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