dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3 08/13] drm/bridge: analogix-anx78xx: Avoid drm_dp_link helpers
Date: Tue, 22 Oct 2019 15:29:06 +0200	[thread overview]
Message-ID: <20191022132906.GK11828@phenom.ffwll.local> (raw)
In-Reply-To: <20191021143437.1477719-9-thierry.reding@gmail.com>

On Mon, Oct 21, 2019 at 04:34:32PM +0200, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
> 
> During the discussion of patches that enhance the drm_dp_link helpers it
> was concluded that these helpers aren't very useful to begin with. Start
> pushing the equivalent code into individual drivers to ultimately remove
> them.
> 
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
>  drivers/gpu/drm/bridge/analogix-anx78xx.c | 57 +++++++++++++++++------
>  1 file changed, 42 insertions(+), 15 deletions(-)
> 
> diff --git a/drivers/gpu/drm/bridge/analogix-anx78xx.c b/drivers/gpu/drm/bridge/analogix-anx78xx.c
> index 9ddc1f3cf841..8bb4793f382b 100644
> --- a/drivers/gpu/drm/bridge/analogix-anx78xx.c
> +++ b/drivers/gpu/drm/bridge/analogix-anx78xx.c
> @@ -71,7 +71,6 @@ struct anx78xx {
>  	struct i2c_client *client;
>  	struct edid *edid;
>  	struct drm_connector connector;
> -	struct drm_dp_link link;
>  	struct anx78xx_platform_data pdata;
>  	struct mutex lock;
>  
> @@ -801,18 +800,34 @@ static int anx78xx_dp_link_training(struct anx78xx *anx78xx)
>  	if (err)
>  		return err;
>  
> -	/* Check link capabilities */
> -	err = drm_dp_link_probe(&anx78xx->aux, &anx78xx->link);
> -	if (err < 0) {
> -		DRM_ERROR("Failed to probe link capabilities: %d\n", err);
> -		return err;
> -	}
> +	/*
> +	 * Power up the sink (DP_SET_POWER register is only available on DPCD
> +	 * v1.1 and later).
> +	 */
> +	if (anx78xx->dpcd[DP_DPCD_REV] >= 0x11) {
> +		err = drm_dp_dpcd_readb(&anx78xx->aux, DP_SET_POWER, &value);
> +		if (err < 0) {
> +			DRM_ERROR("Failed to read DP_SET_POWER register: %d\n",
> +				  err);
> +			return err;
> +		}
>  
> -	/* Power up the sink */
> -	err = drm_dp_link_power_up(&anx78xx->aux, &anx78xx->link);
> -	if (err < 0) {
> -		DRM_ERROR("Failed to power up DisplayPort link: %d\n", err);
> -		return err;
> +		value &= ~DP_SET_POWER_MASK;
> +		value |= DP_SET_POWER_D0;
> +
> +		err = drm_dp_dpcd_writeb(&anx78xx->aux, DP_SET_POWER, value);
> +		if (err < 0) {
> +			DRM_ERROR("Failed to power up DisplayPort link: %d\n",
> +				  err);
> +			return err;
> +		}
> +
> +		/*
> +		 * According to the DP 1.1 specification, a "Sink Device must
> +		 * exit the power saving state within 1 ms" (Section 2.5.3.1,
> +		 * Table 5-52, "Sink Control Field" (register 0x600).
> +		 */
> +		usleep_range(1000, 2000);
>  	}
>  
>  	/* Possibly enable downspread on the sink */
> @@ -851,15 +866,27 @@ static int anx78xx_dp_link_training(struct anx78xx *anx78xx)
>  	if (err)
>  		return err;
>  
> -	value = drm_dp_link_rate_to_bw_code(anx78xx->link.rate);
> +	value = drm_dp_max_link_rate(anx78xx->dpcd);
> +	value = drm_dp_link_rate_to_bw_code(value);
>  	err = regmap_write(anx78xx->map[I2C_IDX_TX_P0],
>  			   SP_DP_MAIN_LINK_BW_SET_REG, value);
>  	if (err)
>  		return err;
>  
> -	err = drm_dp_link_configure(&anx78xx->aux, &anx78xx->link);
> +	err = drm_dp_dpcd_writeb(&anx78xx->aux, DP_LINK_BW_SET, value);
> +	if (err < 0) {
> +		DRM_ERROR("Failed to set link bandwidth: %d\n", err);
> +		return err;
> +	}
> +
> +	value = drm_dp_max_lane_count(anx78xx->dpcd);
> +
> +	if (drm_dp_enhanced_frame_cap(anx78xx->dpcd))
> +		value |= DP_LANE_COUNT_ENHANCED_FRAME_EN;
> +
> +	err = drm_dp_dpcd_writeb(&anx78xx->aux, DP_LANE_COUNT_SET, value);
>  	if (err < 0) {
> -		DRM_ERROR("Failed to configure DisplayPort link: %d\n", err);
> +		DRM_ERROR("Failed to set link lane count: %d\n", err);
>  		return err;

Splits the last two writes into 2 transactions, otherwise looks
equivalent.

Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>

>  	}
>  
> -- 
> 2.23.0
> 

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2019-10-22 13:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-21 14:34 [PATCH v3 00/13] drm/dp: Move drm_dp_link helpers to Tegra DRM Thierry Reding
2019-10-21 14:34 ` [PATCH v3 01/13] drm/dp: Sort includes alphabetically Thierry Reding
2019-10-21 14:34 ` [PATCH v3 02/13] drm/dp: Remove a gratuituous blank line Thierry Reding
2019-10-21 14:34 ` [PATCH v3 03/13] drm/dp: Add drm_dp_fast_training_cap() helper Thierry Reding
2019-10-21 14:34 ` [PATCH v3 04/13] drm/dp: Add drm_dp_channel_coding_supported() helper Thierry Reding
2019-10-21 14:34 ` [PATCH v3 05/13] drm/dp: Add drm_dp_alternate_scrambler_reset_cap() helper Thierry Reding
2019-10-21 14:34 ` [PATCH v3 06/13] drm/dp: Do not busy-loop during link training Thierry Reding
2019-10-22 14:04   ` Daniel Vetter
2019-10-21 14:34 ` [PATCH v3 07/13] drm/dp: Add helper to get post-cursor adjustments Thierry Reding
2019-10-21 14:34 ` [PATCH v3 08/13] drm/bridge: analogix-anx78xx: Avoid drm_dp_link helpers Thierry Reding
2019-10-22 13:29   ` Daniel Vetter [this message]
2019-10-22 14:52     ` [PATCH v4] " Thierry Reding
2019-10-23  9:13       ` Daniel Vetter
2019-10-21 14:34 ` [PATCH v3 09/13] drm/bridge: tc358767: " Thierry Reding
2019-10-22 13:38   ` Daniel Vetter
2019-10-21 14:34 ` [PATCH v3 10/13] drm/bridge: tc358767: Use DP nomenclature Thierry Reding
2019-10-21 14:34 ` [PATCH v3 11/13] drm/msm: edp: Avoid drm_dp_link helpers Thierry Reding
2019-10-22 13:53   ` Daniel Vetter
2019-10-21 14:34 ` [PATCH v3 12/13] drm/rockchip: " Thierry Reding
2019-10-22 14:01   ` Daniel Vetter
2019-10-21 14:34 ` [PATCH v3 13/13] drm/tegra: Move drm_dp_link helpers to Tegra DRM Thierry Reding
2019-10-22 14:03   ` Daniel Vetter

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=20191022132906.GK11828@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=thierry.reding@gmail.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