Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Todd Previte <tprevite@gmail.com>
Cc: intel-gfx@lists.freedesktop.org, 'Rodrigo Vivi' <rodrigo.vivi@intel.com>
Subject: Re: [PATCH] drm/i915: preserve other DP_TEST_SINK bits.
Date: Tue, 30 Sep 2014 09:42:14 +0200	[thread overview]
Message-ID: <20140930074214.GC24667@phenom.ffwll.local> (raw)
In-Reply-To: <009801cfdc36$2f1454c0$8d3cfe40$@gmail.com>

On Mon, Sep 29, 2014 at 03:39:06PM -0700, Todd Previte wrote:
> Hi Rodrigo,
> 
> Looks good. Only thing that needs to be removed is that extra blank line
> between the last part of the function and the return statement. Otherwise...

Looking around in our driver the return statement at the end of the
function is often on a separate line.
> 
> Reviewed-by: Todd Previte <tprevite@gmail.com>

Queued for -next, thanks for the patch.
> 
> -----Original Message-----
> From: Rodrigo Vivi [mailto:rodrigo.vivi@intel.com] 
> Sent: Monday, September 29, 2014 3:30 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: Rodrigo Vivi; Todd Previte
> Subject: [PATCH] drm/i915: preserve other DP_TEST_SINK bits.
> 
> Sink crc was implemented based on dp 1.1 spec that had all TEST_SINK bits
> reserved reading all 0s. But when reviewing my latest changes on sink crc
> Todd warned me that on new specs we have other valid bits on this reg that
> we might want to preserve.

Why was this not mentioned in the review to that patch? I've
double-checked Todd's reply and I've only found a "lgtm, r-b".

If you spot something odd, or something that should be addressed in a
follow-up patch, that should be part of your review reply - review is much
more than rubber-stamping with r-b tags.

And if that review happened offline or in Portland, pls always try to
summarize the main points discussed in the patch or reply for the benefit
of everyone else. We're a globally distributed team, so active and
inclusive communication is absolutely key.

Thanks, Daniel

> 
> Cc: Todd Previte <tprevite@gmail.com>
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
>  drivers/gpu/drm/i915/intel_dp.c | 8 ++++++--
>  1 file changed, 6 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/intel_dp.c
> b/drivers/gpu/drm/i915/intel_dp.c index b8699b0..7d5fa2f 100644
> --- a/drivers/gpu/drm/i915/intel_dp.c
> +++ b/drivers/gpu/drm/i915/intel_dp.c
> @@ -3821,8 +3821,9 @@ int intel_dp_sink_crc(struct intel_dp *intel_dp, u8
> *crc)
>  	if (!(buf & DP_TEST_CRC_SUPPORTED))
>  		return -ENOTTY;
>  
> +	drm_dp_dpcd_readb(&intel_dp->aux, DP_TEST_SINK, &buf);
>  	if (drm_dp_dpcd_writeb(&intel_dp->aux, DP_TEST_SINK,
> -			       DP_TEST_SINK_START) < 0)
> +				buf | DP_TEST_SINK_START) < 0)
>  		return -EIO;
>  
>  	drm_dp_dpcd_readb(&intel_dp->aux, DP_TEST_SINK_MISC, &buf); @@
> -3841,7 +3842,10 @@ int intel_dp_sink_crc(struct intel_dp *intel_dp, u8
> *crc)
>  	if (drm_dp_dpcd_read(&intel_dp->aux, DP_TEST_CRC_R_CR, crc, 6) < 0)
>  		return -EIO;
>  
> -	drm_dp_dpcd_writeb(&intel_dp->aux, DP_TEST_SINK, 0);
> +	drm_dp_dpcd_readb(&intel_dp->aux, DP_TEST_SINK, &buf);
> +	drm_dp_dpcd_writeb(&intel_dp->aux, DP_TEST_SINK,
> +			buf & ~DP_TEST_SINK_START);
> +
>  	return 0;
>  }
>  
> --
> 1.9.3
> 
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2014-09-30  7:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-29 22:29 [PATCH] drm/i915: preserve other DP_TEST_SINK bits Rodrigo Vivi
2014-09-29 22:39 ` Todd Previte
2014-09-30  7:42   ` Daniel Vetter [this message]
2014-09-30 20:36 ` Daniel Vetter
2014-09-30 20:41   ` Rodrigo Vivi
2014-10-01  8:06     ` 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=20140930074214.GC24667@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=tprevite@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