From: Daniel Vetter <daniel@ffwll.ch>
To: Todd Previte <tprevite@gmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/4] drm/i915/dp: increase i2c-over-aux retry interval on AUX DEFER
Date: Fri, 20 Sep 2013 23:53:34 +0200 [thread overview]
Message-ID: <20130920215334.GP32145@phenom.ffwll.local> (raw)
In-Reply-To: <523CB674.90006@gmail.com>
On Fri, Sep 20, 2013 at 01:56:20PM -0700, Todd Previte wrote:
> On 09/20/2013 06:42 AM, Jani Nikula wrote:
> >There is no clear cut rules or specs for the retry interval, as there
> >are many factors that affect overall response time. Increase the
> >interval, and even more so on branch devices which may have limited i2c
> >bit rates.
> >
> >Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> >---
> > drivers/gpu/drm/i915/intel_dp.c | 13 ++++++++++++-
> > 1 file changed, 12 insertions(+), 1 deletion(-)
> >
> >diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
> >index 6626514..3afbea9 100644
> >--- a/drivers/gpu/drm/i915/intel_dp.c
> >+++ b/drivers/gpu/drm/i915/intel_dp.c
> >@@ -678,7 +678,18 @@ intel_dp_i2c_aux_ch(struct i2c_adapter *adapter, int mode,
> > DRM_DEBUG_KMS("aux_ch native nack\n");
> > return -EREMOTEIO;
> > case AUX_NATIVE_REPLY_DEFER:
> >- udelay(100);
> >+ /*
> >+ * For now, just give more slack to branch devices. We
> >+ * could check the DPCD for I2C bit rate capabilities,
> >+ * and if available, adjust the interval. We could also
> >+ * be more careful with DP-to-Legacy adapters where a
> >+ * long legacy cable may force very low I2C bit rates.
> >+ */
> >+ if (intel_dp->dpcd[DP_DOWNSTREAMPORT_PRESENT] &
> >+ DP_DWN_STRM_PORT_PRESENT)
> >+ usleep_range(500, 600);
> >+ else
> >+ usleep_range(300, 400);
> > continue;
> > default:
> > DRM_ERROR("aux_ch invalid native reply 0x%02x\n",
>
> Those look like reasonable values to me.
>
> [Reviewed-by]: Todd Previte <tprevite@gmail.com
> <mailto:tprevite@gmail.com>>
Your mailer sends out html+plaintext multipart mails and in the plaintext
section your r-b tags look rather funny. Can you please fix that?
Thanks, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2013-09-20 21:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-20 13:42 [PATCH 0/4] drm/i915/dp: aux and dpcd fixes Jani Nikula
2013-09-20 13:42 ` [PATCH 1/4] drm/i915/dp: retry i2c-over-aux seven times on AUX DEFER Jani Nikula
2013-09-20 20:38 ` Todd Previte
2013-09-24 6:39 ` Jani Nikula
2013-09-27 11:51 ` Jani Nikula
2013-09-27 19:07 ` Todd Previte
2013-09-27 19:59 ` Daniel Vetter
2013-09-20 13:42 ` [PATCH 2/4] drm/i915/dp: increase i2c-over-aux retry interval " Jani Nikula
2013-09-20 20:56 ` Todd Previte
2013-09-20 21:53 ` Daniel Vetter [this message]
2013-09-20 13:42 ` [PATCH 3/4] drm/i915/dp: downstream port capabilities are not present in DPCD 1.0 Jani Nikula
2013-09-20 13:42 ` [PATCH 4/4] drm/i915/dp: read DPCD PSR capability only on eDP Jani Nikula
2013-09-20 20:50 ` Todd Previte
2013-09-20 20:57 ` Paulo Zanoni
2013-09-20 22:31 ` Todd Previte
2013-09-23 7:29 ` Daniel Vetter
2013-09-23 5:59 ` [PATCH 0/4] drm/i915/dp: aux and dpcd fixes Jani Nikula
2013-09-23 7:30 ` 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=20130920215334.GP32145@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--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