dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Philipp Zabel <p.zabel@pengutronix.de>
To: Andrey Gusakov <andrey.gusakov@cogentembedded.com>
Cc: cphealy@gmail.com, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/6] drm/bridge: tc358767: do no fail on hi-res displays
Date: Tue, 01 Aug 2017 15:11:14 +0200	[thread overview]
Message-ID: <1501593074.3159.40.camel@pengutronix.de> (raw)
In-Reply-To: <20170727124736.3854-2-andrey.gusakov@cogentembedded.com>

On Thu, 2017-07-27 at 15:47 +0300, Andrey Gusakov wrote:
> Do not fail data rates higher than 2.7 and more than 2 lanes.
> Try to fall back to 2.7Gbps and 2 lanes.
> 
> Signed-off-by: Andrey Gusakov <andrey.gusakov@cogentembedded.com>
> ---
>  drivers/gpu/drm/bridge/tc358767.c | 14 +++++++++-----
>  1 file changed, 9 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/gpu/drm/bridge/tc358767.c b/drivers/gpu/drm/bridge/tc358767.c
> index 5c26488e7a2d..f605bb7d1aa3 100644
> --- a/drivers/gpu/drm/bridge/tc358767.c
> +++ b/drivers/gpu/drm/bridge/tc358767.c
> @@ -603,8 +603,15 @@ static int tc_get_display_props(struct tc_data *tc)
>  	ret = drm_dp_link_probe(&tc->aux, &tc->link.base);
>  	if (ret < 0)
>  		goto err_dpcd_read;
> -	if ((tc->link.base.rate != 162000) && (tc->link.base.rate != 270000))
> -		goto err_dpcd_inval;
> +	if ((tc->link.base.rate != 162000) && (tc->link.base.rate != 270000)) {
> +		dev_dbg(tc->dev, "Falling to 2.7 Gbps rate\n");
> +		tc->link.base.rate = 270000;
> +	}
> +
> +	if (tc->link.base.num_lanes > 2) {
> +		dev_dbg(tc->dev, "Falling to 2 lanes\n");
> +		tc->link.base.num_lanes = 2;
> +	}
>  
>  	ret = drm_dp_dpcd_readb(&tc->aux, DP_MAX_DOWNSPREAD, tmp);
>  	if (ret < 0)
> @@ -637,9 +644,6 @@ static int tc_get_display_props(struct tc_data *tc)
>  err_dpcd_read:
>  	dev_err(tc->dev, "failed to read DPCD: %d\n", ret);
>  	return ret;
> -err_dpcd_inval:
> -	dev_err(tc->dev, "invalid DPCD\n");
> -	return -EINVAL;
>  }
>  
>  static int tc_set_video_mode(struct tc_data *tc, struct drm_display_mode *mode)

Acked-by: Philipp Zabel <p.zabel@pengutronix.de>

regards
Philipp

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2017-08-01 13:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-27 12:47 [PATCH 0/6] drm/bridge: tc358767: fixes and improvements Andrey Gusakov
2017-07-27 12:47 ` [PATCH 1/6] drm/bridge: tc358767: do no fail on hi-res displays Andrey Gusakov
2017-08-01 13:11   ` Philipp Zabel [this message]
2017-07-27 12:47 ` [PATCH 2/6] drm/bridge: tc358767: filter out too high modes Andrey Gusakov
2017-08-01 13:11   ` Philipp Zabel
2017-08-02 17:34     ` Andrey Gusakov
2017-07-27 12:47 ` [PATCH 3/6] drm/bridge: tc358767: fix DP0_MISC register set Andrey Gusakov
2017-08-01 13:11   ` Philipp Zabel
2017-07-27 12:47 ` [PATCH 4/6] drm/bridge: tc358767: fix timing calculations Andrey Gusakov
2017-08-01 13:12   ` Philipp Zabel
2017-07-27 12:47 ` [PATCH 5/6] drm/bridge: tc358767: fix AUXDATAn registers access Andrey Gusakov
2017-08-01 13:12   ` Philipp Zabel
2017-07-27 12:47 ` [PATCH 6/6] drm/bridge: tc358767: fix 1-lane behavior Andrey Gusakov
2017-08-01 13:13   ` Philipp Zabel
2017-08-01  5:06 ` [PATCH 0/6] drm/bridge: tc358767: fixes and improvements Archit Taneja

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=1501593074.3159.40.camel@pengutronix.de \
    --to=p.zabel@pengutronix.de \
    --cc=andrey.gusakov@cogentembedded.com \
    --cc=cphealy@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    /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