dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Paul <sean@poorly.run>
To: Heiko Stuebner <heiko@sntech.de>
Cc: Zain Wang <wzz@rock-chips.com>, David Airlie <airlied@linux.ie>,
	dri-devel@lists.freedesktop.org, Tomasz Figa <tfiga@chromium.org>,
	Sean Paul <seanpaul@chromium.org>,
	Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
	Sean Paul <sean@poorly.run>
Subject: Re: [PATCH v5 07/11] drm/rockchip: Check for fast link training before enabling psr
Date: Fri, 26 Jul 2019 14:52:17 -0400	[thread overview]
Message-ID: <20190726185217.GP104440@art_vandelay> (raw)
In-Reply-To: <3530881.Ri8gbRaMhX@phil>

On Thu, Jul 25, 2019 at 08:39:42PM +0200, Heiko Stuebner wrote:
> Hi Sean,
> 
> Am Donnerstag, 25. Juli 2019, 20:08:12 CEST schrieb Sean Paul:
> > On Tue, Jun 11, 2019 at 12:08:21PM -0400, Sean Paul wrote:
> > > From: Sean Paul <seanpaul@chromium.org>
> > > 
> > > Once we start shutting off the link during PSR, we're going to want fast
> > > training to work. If the display doesn't support fast training, don't
> > > enable psr.
> > > 
> > > Changes in v2:
> > > - None
> > > Changes in v3:
> > > - None
> > > Changes in v4:
> > > - None
> > > Changes in v5:
> > > - None
> > > 
> > > Link to v1: https://patchwork.freedesktop.org/patch/msgid/20190228210939.83386-3-sean@poorly.run
> > > Link to v2: https://patchwork.freedesktop.org/patch/msgid/20190326204509.96515-2-sean@poorly.run
> > > Link to v3: https://patchwork.freedesktop.org/patch/msgid/20190502194956.218441-9-sean@poorly.run
> > > Link to v4: https://patchwork.freedesktop.org/patch/msgid/20190508160920.144739-8-sean@poorly.run
> > > 
> > > Cc: Zain Wang <wzz@rock-chips.com>
> > > Cc: Tomasz Figa <tfiga@chromium.org>
> > > Tested-by: Heiko Stuebner <heiko@sntech.de>
> > 
> > @Heiko, could you please review patches 7-11? I'm worried they're going to start
> > to rot and the helpers have already landed in Linus' tree.
> 
> I did look through the patches and nothing out of the ordinary sprang
> out to my (somewhat untrained) eye and judging by my tested-tags I also
> gave them a spin at some point - although it seems I never was actually on
> cc for them.
> 
> In any case they look good to me, so if it helps you, you can add my
> 	Reviewed-by: Heiko Stuebner <heiko@sntech.de>
> though should take the technical expertise on drm-internals with a
> grain of salt.

Thanks Heiko! Given how long this has been on the list and that both you and I
have tested it, I've pushed it to drm-misc-next with your R-b. I'll keep an eye
on things as it rolls out and hopefully everything will go smoothly.

Sean

> 
> 
> Heiko
> 
> 
> 
> > > Signed-off-by: Sean Paul <seanpaul@chromium.org>
> > > ---
> > >  drivers/gpu/drm/bridge/analogix/analogix_dp_core.c | 9 +++++----
> > >  1 file changed, 5 insertions(+), 4 deletions(-)
> > > 
> > > diff --git a/drivers/gpu/drm/bridge/analogix/analogix_dp_core.c b/drivers/gpu/drm/bridge/analogix/analogix_dp_core.c
> > > index d2de98d441845..a07d19e08b803 100644
> > > --- a/drivers/gpu/drm/bridge/analogix/analogix_dp_core.c
> > > +++ b/drivers/gpu/drm/bridge/analogix/analogix_dp_core.c
> > > @@ -1040,16 +1040,17 @@ static int analogix_dp_commit(struct analogix_dp_device *dp)
> > >  	if (ret)
> > >  		return ret;
> > >  
> > > +	/* Check whether panel supports fast training */
> > > +	ret = analogix_dp_fast_link_train_detection(dp);
> > > +	if (ret)
> > > +		dp->psr_enable = false;
> > > +
> > >  	if (dp->psr_enable) {
> > >  		ret = analogix_dp_enable_sink_psr(dp);
> > >  		if (ret)
> > >  			return ret;
> > >  	}
> > >  
> > > -	/* Check whether panel supports fast training */
> > > -	ret =  analogix_dp_fast_link_train_detection(dp);
> > > -	if (ret)
> > > -		dp->psr_enable = false;
> > >  
> > >  	return ret;
> > >  }
> > 
> > 
> 
> 
> 
> 

-- 
Sean Paul, Software Engineer, Google / Chromium OS
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2019-07-26 18:52 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-11 16:08 [PATCH v5 00/11] drm: Add self refresh helpers Sean Paul
2019-06-11 16:08 ` [PATCH v5 01/11] drm: Add atomic variants of enable/disable to encoder helper funcs Sean Paul
2019-06-11 18:53   ` Sam Ravnborg
2019-06-11 20:22     ` Sean Paul
2019-06-11 20:49     ` [PATCH v6 " Sean Paul
2019-06-11 16:08 ` [PATCH v5 02/11] drm: Add drm_atomic_get_(old|new_connector_for_encoder() helpers Sean Paul
2019-06-11 18:57   ` Sam Ravnborg
2019-06-11 20:51     ` [PATCH v6 02/11] drm: Add drm_atomic_get_(old|new)_connector_for_encoder() helpers Sean Paul
2019-06-11 16:08 ` [PATCH v5 03/11] drm: Add atomic variants for bridge enable/disable Sean Paul
2019-06-11 16:08 ` [PATCH v5 04/11] drm: Convert connector_helper_funcs->atomic_check to accept drm_atomic_state Sean Paul
2019-06-11 17:58   ` Laurent Pinchart
2019-06-11 16:08 ` [PATCH v5 05/11] drm: Add helpers to kick off self refresh mode in drivers Sean Paul
2019-06-11 20:56   ` Sam Ravnborg
2019-06-12 14:19     ` Sean Paul
2019-06-12 14:50     ` [PATCH v6] " Sean Paul
2019-06-11 16:08 ` [PATCH v5 06/11] drm/rockchip: Use dirtyfb helper Sean Paul
2019-06-11 17:39   ` Daniel Vetter
2019-06-11 18:09     ` Sean Paul
2019-06-11 16:08 ` [PATCH v5 07/11] drm/rockchip: Check for fast link training before enabling psr Sean Paul
2019-07-25 18:08   ` Sean Paul
2019-07-25 18:39     ` Heiko Stuebner
2019-07-26 18:52       ` Sean Paul [this message]
2019-06-11 16:08 ` [PATCH v5 08/11] drm/rockchip: Use the helpers for PSR Sean Paul
2019-06-11 16:08 ` [PATCH v5 09/11] drm/rockchip: Use vop_win in vop_win_disable instead of vop_win_data Sean Paul
2019-06-11 16:08 ` [PATCH v5 10/11] drm/rockchip: Don't fully disable vop on self refresh Sean Paul
2019-06-11 16:08 ` [PATCH v5 11/11] drm/rockchip: Use drm_atomic_helper_commit_tail_rpm Sean Paul
2019-06-13 19:05 ` [PATCH v5 00/11] drm: Add self refresh helpers Sean Paul

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=20190726185217.GP104440@art_vandelay \
    --to=sean@poorly.run \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=heiko@sntech.de \
    --cc=seanpaul@chromium.org \
    --cc=tfiga@chromium.org \
    --cc=wzz@rock-chips.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