All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Paul <sean@poorly.run>
To: Ramalingam C <ramalingam.c@intel.com>
Cc: daniel.vetter@ffwll.ch, intel-gfx@lists.freedesktop.org,
	seanpaul@chromium.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 3/4] drm/i915: debug log for REPLY_ACK missing
Date: Mon, 3 Dec 2018 09:26:26 -0500	[thread overview]
Message-ID: <20181203142626.GO154160@art_vandelay> (raw)
In-Reply-To: <1543327379-22629-4-git-send-email-ramalingam.c@intel.com>

On Tue, Nov 27, 2018 at 07:32:58PM +0530, Ramalingam C wrote:
> Adding a debug log when the DP_AUX_NATIVE_REPLY_ACK is missing
> for aksv write. This helps to locate the possible non responding
> DP HDCP sinks.
> 
> Signed-off-by: Ramalingam C <ramalingam.c@intel.com>
> ---
>  drivers/gpu/drm/i915/intel_dp.c | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
> index 70ae3d57316b..18e3a5a3d873 100644
> --- a/drivers/gpu/drm/i915/intel_dp.c
> +++ b/drivers/gpu/drm/i915/intel_dp.c
> @@ -5390,7 +5390,11 @@ int intel_dp_hdcp_write_an_aksv(struct intel_digital_port *intel_dig_port,
>  	}
>  
>  	reply = (rxbuf[0] >> 4) & DP_AUX_NATIVE_REPLY_MASK;
> -	return reply == DP_AUX_NATIVE_REPLY_ACK ? 0 : -EIO;
> +	ret = reply == DP_AUX_NATIVE_REPLY_ACK ? 0 : -EIO;
> +	if (ret)
> +		DRM_DEBUG_KMS("Aksv write: DP_AUX_NATIVE_REPLY_ACK missing\n");

This is pretty hard to read. Could you please change to:

        if (reply != DP_AUX_NATIVE_REPLY_ACK) {
                DRM_DEBUG_KMS("Aksv write: no DP_AUX_NATIVE_REPLY_ACK %x\n",
                              reply);
                return -EIO
        }
        return 0;

With this change,

Reviewed-by: Sean Paul <sean@poorly.run>


> +
> +	return ret;
>  }
>  
>  static int intel_dp_hdcp_read_bksv(struct intel_digital_port *intel_dig_port,
> -- 
> 2.7.4
> 
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel

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

  reply	other threads:[~2018-12-03 14:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-27 14:02 [PATCH 0/4] HDCP1.4 fixes Ramalingam C
2018-11-27 14:02 ` [PATCH 1/4] drm/i915: Fix GEN9 HDCP1.4 key load process Ramalingam C
2018-11-27 15:15   ` Ville Syrjälä
2018-11-27 16:27     ` [Intel-gfx] " C, Ramalingam
2018-11-28 14:00   ` [PATCH v2 " Ramalingam C
2018-12-03 14:23   ` [PATCH " Sean Paul
2018-11-27 14:02 ` [PATCH 2/4] drm/i915: Fix platform coverage for HDCP1.4 Ramalingam C
2018-12-03 14:23   ` Sean Paul
2018-11-27 14:02 ` [PATCH 3/4] drm/i915: debug log for REPLY_ACK missing Ramalingam C
2018-12-03 14:26   ` Sean Paul [this message]
2018-11-27 14:02 ` [PATCH 4/4] drm/i915: Increase timeout for Encrypt status change Ramalingam C
2018-12-03 14:27   ` Sean Paul
2018-11-27 14:36 ` ✓ Fi.CI.BAT: success for HDCP1.4 fixes (rev8) Patchwork
2018-11-27 17:52 ` ✓ Fi.CI.IGT: " Patchwork
2018-11-28 16:10 ` ✓ Fi.CI.BAT: success for HDCP1.4 fixes (rev9) Patchwork
2018-11-29  0:10 ` ✓ Fi.CI.IGT: " Patchwork
2018-12-03 10:08 ` [PATCH 0/4] HDCP1.4 fixes C, Ramalingam

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=20181203142626.GO154160@art_vandelay \
    --to=sean@poorly.run \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ramalingam.c@intel.com \
    --cc=seanpaul@chromium.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 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.