From: Daniel Vetter <daniel@ffwll.ch>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Alex Deucher <alexander.deucher@amd.com>,
christian.koenig@amd.com, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/dp: make aux retries less chatty
Date: Fri, 21 Mar 2014 19:01:32 +0100 [thread overview]
Message-ID: <20140321180116.GA26519@phenom.ffwll.local> (raw)
In-Reply-To: <1395412448-28048-1-git-send-email-alexander.deucher@amd.com>
On Fri, Mar 21, 2014 at 10:34:06AM -0400, Alex Deucher wrote:
> Switch to debug only to avoid flooding the logs.
> This mirrors the behavior in some other drivers.
>
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Btw I've just noticed that we have a 2nd retry loop with 3 retries and a 1
msec delay which apparently is needed to kick suspended dp sinks out of
their sleep. See intel_dp_dpcd_read_wake in intel_dp.c. Should we maybe
move that 2nd loop into these helpers, too?
-Daniel
> ---
> drivers/gpu/drm/drm_dp_helper.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_dp_helper.c b/drivers/gpu/drm/drm_dp_helper.c
> index 35251af..74724aa 100644
> --- a/drivers/gpu/drm/drm_dp_helper.c
> +++ b/drivers/gpu/drm/drm_dp_helper.c
> @@ -402,7 +402,7 @@ static int drm_dp_dpcd_access(struct drm_dp_aux *aux, u8 request,
> }
> }
>
> - DRM_ERROR("too many retries, giving up\n");
> + DRM_DEBUG_KMS("too many retries, giving up\n");
> return -EIO;
> }
>
> @@ -656,7 +656,7 @@ static int drm_dp_i2c_do_msg(struct drm_dp_aux *aux, struct drm_dp_aux_msg *msg)
> }
> }
>
> - DRM_ERROR("too many retries, giving up\n");
> + DRM_DEBUG_KMS("too many retries, giving up\n");
> return -EREMOTEIO;
> }
>
> --
> 1.8.3.1
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-03-21 18:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 14:34 [PATCH 1/3] drm/dp: make aux retries less chatty Alex Deucher
2014-03-21 14:34 ` [PATCH 2/3] drm/radeon: use the new drm helpers for dp aux Alex Deucher
2014-03-21 14:34 ` [PATCH 3/3] drm/radeon: use drm_dp_dpcd_read_link_status() Alex Deucher
2014-03-21 18:01 ` Daniel Vetter [this message]
2014-03-21 19:06 ` [PATCH 1/3] drm/dp: make aux retries less chatty Christian König
-- strict thread matches above, loose matches on Subject: below --
2014-03-18 3:51 Alex Deucher
2014-03-18 7:44 ` Jani Nikula
2014-03-19 13:42 ` Alex Deucher
2014-03-19 14:02 ` Daniel Vetter
2014-03-19 14:21 ` 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=20140321180116.GA26519@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=christian.koenig@amd.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