All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>,
	intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Cc: ankit.k.nautiyal@intel.com, chaitanya.kumar.borah@intel.com,
	dnyaneshwar.bhadane@intel.com,
	Suraj Kandpal <suraj.kandpal@intel.com>
Subject: Re: [PATCH 1/2] drm/i915/dp: Use intel_display instead of drm_i915_private
Date: Fri, 03 Jan 2025 12:08:17 +0200	[thread overview]
Message-ID: <87pll4mcq6.fsf@intel.com> (raw)
In-Reply-To: <20250103051705.145161-2-suraj.kandpal@intel.com>

On Fri, 03 Jan 2025, Suraj Kandpal <suraj.kandpal@intel.com> wrote:
> Use intel display instead of drm_i915_private in
> mtl_ddi_prepare_link_retrain & mtl_port_buf_ctl_program
> functions.
>
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>

This is a good direction, but I'd aim higher than just a few
functions...

Reviewed-by: Jani Nikula <jani.nikula@intel.com>

> ---
>  drivers/gpu/drm/i915/display/intel_ddi.c | 20 ++++++++++----------
>  1 file changed, 10 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_ddi.c b/drivers/gpu/drm/i915/display/intel_ddi.c
> index 4f9c50996446..5e944cae116a 100644
> --- a/drivers/gpu/drm/i915/display/intel_ddi.c
> +++ b/drivers/gpu/drm/i915/display/intel_ddi.c
> @@ -2534,12 +2534,12 @@ mtl_ddi_enable_d2d(struct intel_encoder *encoder)
>  static void mtl_port_buf_ctl_program(struct intel_encoder *encoder,
>  				     const struct intel_crtc_state *crtc_state)
>  {
> -	struct drm_i915_private *i915 = to_i915(encoder->base.dev);
> +	struct intel_display *display = to_intel_display(encoder);
>  	struct intel_digital_port *dig_port = enc_to_dig_port(encoder);
>  	enum port port = encoder->port;
>  	u32 val;
>  
> -	val = intel_de_read(i915, XELPDP_PORT_BUF_CTL1(i915, port));
> +	val = intel_de_read(display, XELPDP_PORT_BUF_CTL1(i915, port));
>  	val &= ~XELPDP_PORT_WIDTH_MASK;
>  	val |= XELPDP_PORT_WIDTH(mtl_get_port_width(crtc_state->lane_count));
>  
> @@ -2552,7 +2552,7 @@ static void mtl_port_buf_ctl_program(struct intel_encoder *encoder,
>  	if (dig_port->lane_reversal)
>  		val |= XELPDP_PORT_REVERSAL;
>  
> -	intel_de_write(i915, XELPDP_PORT_BUF_CTL1(i915, port), val);
> +	intel_de_write(display, XELPDP_PORT_BUF_CTL1(display, port), val);
>  }
>  
>  static void mtl_port_buf_ctl_io_selection(struct intel_encoder *encoder)
> @@ -3639,9 +3639,9 @@ static void adlp_tbt_to_dp_alt_switch_wa(struct intel_encoder *encoder)
>  static void mtl_ddi_prepare_link_retrain(struct intel_dp *intel_dp,
>  					 const struct intel_crtc_state *crtc_state)
>  {
> +	struct intel_display *display = to_intel_display(crtc_state);
>  	struct intel_digital_port *dig_port = dp_to_dig_port(intel_dp);
>  	struct intel_encoder *encoder = &dig_port->base;
> -	struct drm_i915_private *dev_priv = to_i915(encoder->base.dev);
>  	enum port port = encoder->port;
>  	u32 dp_tp_ctl;
>  
> @@ -3649,7 +3649,7 @@ static void mtl_ddi_prepare_link_retrain(struct intel_dp *intel_dp,
>  	 * TODO: To train with only a different voltage swing entry is not
>  	 * necessary disable and enable port
>  	 */
> -	dp_tp_ctl = intel_de_read(dev_priv, dp_tp_ctl_reg(encoder, crtc_state));
> +	dp_tp_ctl = intel_de_read(display, dp_tp_ctl_reg(encoder, crtc_state));
>  	if (dp_tp_ctl & DP_TP_CTL_ENABLE)
>  		mtl_disable_ddi_buf(encoder, crtc_state);
>  
> @@ -3662,8 +3662,8 @@ static void mtl_ddi_prepare_link_retrain(struct intel_dp *intel_dp,
>  		if (crtc_state->enhanced_framing)
>  			dp_tp_ctl |= DP_TP_CTL_ENHANCED_FRAME_ENABLE;
>  	}
> -	intel_de_write(dev_priv, dp_tp_ctl_reg(encoder, crtc_state), dp_tp_ctl);
> -	intel_de_posting_read(dev_priv, dp_tp_ctl_reg(encoder, crtc_state));
> +	intel_de_write(display, dp_tp_ctl_reg(encoder, crtc_state), dp_tp_ctl);
> +	intel_de_posting_read(display, dp_tp_ctl_reg(encoder, crtc_state));
>  
>  	/* 6.f Enable D2D Link */
>  	mtl_ddi_enable_d2d(encoder);
> @@ -3676,11 +3676,11 @@ static void mtl_ddi_prepare_link_retrain(struct intel_dp *intel_dp,
>  
>  	/* 6.i Configure and enable DDI_CTL_DE to start sending valid data to port slice */
>  	intel_dp->DP |= DDI_BUF_CTL_ENABLE;
> -	if (DISPLAY_VER(dev_priv) >= 20)
> +	if (DISPLAY_VER(display) >= 20)
>  		intel_dp->DP |= XE2LPD_DDI_BUF_D2D_LINK_ENABLE;
>  
> -	intel_de_write(dev_priv, DDI_BUF_CTL(port), intel_dp->DP);
> -	intel_de_posting_read(dev_priv, DDI_BUF_CTL(port));
> +	intel_de_write(display, DDI_BUF_CTL(port), intel_dp->DP);
> +	intel_de_posting_read(display, DDI_BUF_CTL(port));
>  
>  	/* 6.j Poll for PORT_BUF_CTL Idle Status == 0, timeout after 100 us */
>  	intel_wait_ddi_buf_active(encoder);

-- 
Jani Nikula, Intel

  reply	other threads:[~2025-01-03 10:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-03  5:17 [PATCH 0/2] Clean and Optimise mtl_ddi_prepare_link_retrain Suraj Kandpal
2025-01-03  5:17 ` [PATCH 1/2] drm/i915/dp: Use intel_display instead of drm_i915_private Suraj Kandpal
2025-01-03 10:08   ` Jani Nikula [this message]
2025-01-03  5:17 ` [PATCH 2/2] drm/i915/ddi: Optimize mtl_port_buf_ctl_program Suraj Kandpal
2025-01-03 10:08   ` Jani Nikula
2025-01-03  6:21 ` ✓ CI.Patch_applied: success for Clean and Optimise mtl_ddi_prepare_link_retrain Patchwork
2025-01-03  6:21 ` ✓ CI.checkpatch: " Patchwork
2025-01-03  6:23 ` ✓ CI.KUnit: " Patchwork
2025-01-03  6:41 ` ✓ CI.Build: " Patchwork
2025-01-03  6:43 ` ✓ CI.Hooks: " Patchwork
2025-01-03  6:45 ` ✓ CI.checksparse: " Patchwork
2025-01-03  7:01 ` ✗ i915.CI.BAT: failure " Patchwork
2025-01-03  7:17 ` ✗ Xe.CI.BAT: " Patchwork
2025-01-03  8:50 ` ✗ Xe.CI.Full: " Patchwork
2025-01-06 10:38 ` ✓ i915.CI.BAT: success " Patchwork
2025-01-06 14:59 ` ✗ i915.CI.Full: 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=87pll4mcq6.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=ankit.k.nautiyal@intel.com \
    --cc=chaitanya.kumar.borah@intel.com \
    --cc=dnyaneshwar.bhadane@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=suraj.kandpal@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.