Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Damien Lespiau <damien.lespiau@gmail.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 4/4] drm/i915/dp: Don't log the DPCD if we are disconnected
Date: Thu, 13 Dec 2012 10:33:34 +0200	[thread overview]
Message-ID: <87body4aht.fsf@intel.com> (raw)
In-Reply-To: <1355341841-4595-4-git-send-email-damien.lespiau@gmail.com>

On Wed, 12 Dec 2012, Damien Lespiau <damien.lespiau@gmail.com> wrote:
> From: Damien Lespiau <damien.lespiau@intel.com>
>
> It's a bit useless to print out an all null DPCD when we are
> disconnected and just clutter the debug logs.

NAK.

Please have a look at intel_dp_detect_dpcd(). There are a number of ways
to get a non-zero DPCD that lead to something other than
connector_status_connected. The comment says, "XXX this is probably
wrong for multiple downstream ports", so there's also some work to do in
the area. IMO we need the debugs.

Even intel_dp_get_dpcd() has one branch that returns false when we have
non-zero DPCD. But if we ignored that part (it's an aux channel error
anyway), we could move the debug dump to intel_dp_detect_dpcd() right
after the intel_dp_get_dpcd() call. I think that would get maximum debug
coverage with minimum zero DPCD noise.

What do you think?


BR,
Jani.



>
> Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
> ---
>  drivers/gpu/drm/i915/intel_dp.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
> index fe3c22f..42058fa 100644
> --- a/drivers/gpu/drm/i915/intel_dp.c
> +++ b/drivers/gpu/drm/i915/intel_dp.c
> @@ -2362,13 +2362,13 @@ intel_dp_detect(struct drm_connector *connector, bool force)
>  	else
>  		status = g4x_dp_detect(intel_dp);
>  
> +	if (status != connector_status_connected)
> +		return status;
> +
>  	hex_dump_to_buffer(intel_dp->dpcd, sizeof(intel_dp->dpcd),
>  			   32, 1, dpcd_hex_dump, sizeof(dpcd_hex_dump), false);
>  	DRM_DEBUG_KMS("DPCD: %s\n", dpcd_hex_dump);
>  
> -	if (status != connector_status_connected)
> -		return status;
> -
>  	intel_dp_probe_oui(intel_dp);
>  
>  	if (intel_dp->force_audio != HDMI_AUDIO_AUTO) {
> -- 
> 1.7.11.7
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2012-12-13  8:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-12 19:50 [PATCH 1/4] drm/i915: Cleanup SHOTPLUG_CTL status bits definitions Damien Lespiau
2012-12-12 19:50 ` [PATCH 2/4] drm/i915/hdmi: Read the HPD status before trying to read the EDID Damien Lespiau
2012-12-13  8:40   ` Chris Wilson
2012-12-13 11:11   ` Jani Nikula
2012-12-12 19:50 ` [PATCH 3/4] drm/i915/dp: Read the HPD status before trying to read the DPCD Damien Lespiau
2012-12-13 11:16   ` Jani Nikula
2012-12-12 19:50 ` [PATCH 4/4] drm/i915/dp: Don't log the DPCD if we are disconnected Damien Lespiau
2012-12-13  8:33   ` Jani Nikula [this message]
2012-12-13  8:39 ` [PATCH 1/4] drm/i915: Cleanup SHOTPLUG_CTL status bits definitions Jani Nikula

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=87body4aht.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=damien.lespiau@gmail.com \
    --cc=intel-gfx@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