public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Kulkarni, Vandita" <vandita.kulkarni@intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Fix TGL DKL PHY DP vswing handling
Date: Thu, 1 Oct 2020 04:05:53 +0000	[thread overview]
Message-ID: <86c6be4ebc1f416a8156b748e95738af@intel.com> (raw)
In-Reply-To: <20200930223642.28565-1-ville.syrjala@linux.intel.com>

> -----Original Message-----
> From: Ville Syrjala <ville.syrjala@linux.intel.com>
> Sent: Thursday, October 1, 2020 4:07 AM
> To: intel-gfx@lists.freedesktop.org
> Cc: stable@vger.kernel.org; Kulkarni, Vandita <vandita.kulkarni@intel.com>;
> Shankar, Uma <uma.shankar@intel.com>
> Subject: [PATCH] drm/i915: Fix TGL DKL PHY DP vswing handling
> 
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> 
> The HDMI vs. not-HDMI check got inverted whem the bogus encoder->type
> checks were eliminated. So now we're using 0 as the link rate on DP and
> potentially non-zero on HDMI, which is exactly the opposite of what we
> want. The original bogus check actually worked more correctly by accident
> since if would always evaluate to true. Due to this we now always use the
> RBR/HBR1 vswing table and never ever the HBR2+ vswing table. That is
> probably not a good way to get a high quality signal at HBR2+ rates. Fix the
> check so we pick the right table.
> 
> Cc: stable@vger.kernel.org
> Cc: Vandita Kulkarni <vandita.kulkarni@intel.com>
> Cc: Uma Shankar <uma.shankar@intel.com>
> Fixes: 94641eb6c696 ("drm/i915/display: Fix the encoder type check")
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

LGTM.
Reviewed-by: Vandita Kulkarni <vandita.kulkarni@intel.com>
I think I missed the inverted change while rebasing.
Thanks,
Vandita
> ---
>  drivers/gpu/drm/i915/display/intel_ddi.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_ddi.c
> b/drivers/gpu/drm/i915/display/intel_ddi.c
> index 4d06178cd76c..cdcb7b1034ae 100644
> --- a/drivers/gpu/drm/i915/display/intel_ddi.c
> +++ b/drivers/gpu/drm/i915/display/intel_ddi.c
> @@ -2742,7 +2742,7 @@ tgl_dkl_phy_ddi_vswing_sequence(struct
> intel_encoder *encoder, int link_clock,
>  	u32 n_entries, val, ln, dpcnt_mask, dpcnt_val;
>  	int rate = 0;
> 
> -	if (type == INTEL_OUTPUT_HDMI) {
> +	if (type != INTEL_OUTPUT_HDMI) {
>  		struct intel_dp *intel_dp = enc_to_intel_dp(encoder);
> 
>  		rate = intel_dp->link_rate;
> --
> 2.26.2

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2020-10-01  4:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-30 22:36 [Intel-gfx] [PATCH] drm/i915: Fix TGL DKL PHY DP vswing handling Ville Syrjala
2020-09-30 22:48 ` Souza, Jose
2020-09-30 23:19 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-10-01  4:05 ` Kulkarni, Vandita [this message]
2020-10-01  5:15 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=86c6be4ebc1f416a8156b748e95738af@intel.com \
    --to=vandita.kulkarni@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=stable@vger.kernel.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