public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Imre Deak <imre.deak@intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 3/4] drm/i915: Remove DP_PORT_EN stuff from link training code
Date: Thu, 30 Sep 2021 19:09:03 +0300	[thread overview]
Message-ID: <20210930160903.GE2418125@ideak-desk.fi.intel.com> (raw)
In-Reply-To: <20210930134310.31669-3-ville.syrjala@linux.intel.com>

On Thu, Sep 30, 2021 at 04:43:09PM +0300, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> 
> Setting DP_PORT_EN in intel_dp->DP is already handled by
> intel_dp_enable_port() so there is no point in setting it also
> from the link training code.
> 
> For DDI platforms a bit with that name doesn't even exist. The
> counterpart is DDI_BUF_CTL_ENABLE, which is already set up by
> intel_ddi_prepare_link_retrain(). Fortunately it is the same bit
> so there was no harm in doing this from the platform independent
> code as well. But it's just confusing when platform independent
> code sets platform specific bits in intel_dp->DP. Just get rid
> of it.
> 
> Cc: Imre Deak <imre.deak@intel.com>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

Reviewed-by: Imre Deak <imre.deak.intel.com>

On pre-DDI platforms intel_dp_enable_port() may not be called before
short HPD/link-retraining, but the init/resume time HW readout will
set DP_PORT_EN for that case.

> ---
>  drivers/gpu/drm/i915/display/intel_dp_link_training.c | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_dp_link_training.c b/drivers/gpu/drm/i915/display/intel_dp_link_training.c
> index 449499a5c4c1..053ed9302cda 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp_link_training.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp_link_training.c
> @@ -499,8 +499,6 @@ intel_dp_prepare_link_train(struct intel_dp *intel_dp,
>  		DP_SET_ANSI_128B132B : DP_SET_ANSI_8B10B;
>  	drm_dp_dpcd_write(&intel_dp->aux, DP_DOWNSPREAD_CTRL, link_config, 2);
>  
> -	intel_dp->DP |= DP_PORT_EN;
> -
>  	return true;
>  }
>  
> -- 
> 2.32.0
> 

  reply	other threads:[~2021-09-30 16:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-30 13:43 [Intel-gfx] [PATCH 1/4] drm/i915: Clear leftover DP vswing/preemphasis values before modeset Ville Syrjala
2021-09-30 13:43 ` [Intel-gfx] [PATCH 2/4] drm/i915: Call intel_ddi_init_dp_buf_reg() earlier Ville Syrjala
2021-09-30 15:51   ` Imre Deak
2021-09-30 13:43 ` [Intel-gfx] [PATCH 3/4] drm/i915: Remove DP_PORT_EN stuff from link training code Ville Syrjala
2021-09-30 16:09   ` Imre Deak [this message]
2021-09-30 16:16     ` Ville Syrjälä
2021-09-30 16:19       ` Imre Deak
2021-09-30 16:21         ` Imre Deak
2021-09-30 13:43 ` [Intel-gfx] [PATCH 4/4] drm/i915: Nuke local copies/pointers of intel_dp->DP Ville Syrjala
2021-09-30 16:15   ` Imre Deak
2021-09-30 15:25 ` [Intel-gfx] [PATCH 1/4] drm/i915: Clear leftover DP vswing/preemphasis values before modeset Imre Deak
2021-09-30 16:15 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/4] " Patchwork
2021-09-30 19:49 ` [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=20210930160903.GE2418125@ideak-desk.fi.intel.com \
    --to=imre.deak@intel.com \
    --cc=intel-gfx@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