Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Almahallawy, Khaled" <khaled.almahallawy@intel.com>
To: "dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"tzimmermann@suse.de" <tzimmermann@suse.de>
Cc: "seanpaul@chromium.org" <seanpaul@chromium.org>
Subject: Re: [Intel-gfx] [RFC PATCH 1/2] drm/dp: Make number of AUX retries configurable by display drivers.
Date: Wed, 10 Feb 2021 10:16:15 +0000	[thread overview]
Message-ID: <a24dffd636a8999fd2eeedb04ceb813906d711e3.camel@intel.com> (raw)
In-Reply-To: <9c290abd-7770-e386-76a4-c821ab33752b@suse.de>

On Wed, 2021-02-10 at 09:55 +0100, Thomas Zimmermann wrote:
> Hi
> 
> Am 10.02.21 um 09:33 schrieb Khaled Almahallawy:
> > The number of AUX retries specified in the DP specs is 7.
> > Currently, to make Dell 4k monitors happier, the number of retries
> > are 32.
> > i915 also retries 5 times (intel_dp_aux_xfer) which means in the
> > case of AUX timeout we actually retries 32 * 5 = 160 times.
> > 
> > So making the number of aux retires a variable to allow for fine
> > tuning and optimization of aux timing.
> > 
> > Signed-off-by: Khaled Almahallawy <khaled.almahallawy@intel.com>
> > ---
> >   drivers/gpu/drm/drm_dp_helper.c | 10 +++-------
> >   include/drm/drm_dp_helper.h     |  1 +
> >   2 files changed, 4 insertions(+), 7 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/drm_dp_helper.c
> > b/drivers/gpu/drm/drm_dp_helper.c
> > index eedbb48815b7..8fdf57b4a06c 100644
> > --- a/drivers/gpu/drm/drm_dp_helper.c
> > +++ b/drivers/gpu/drm/drm_dp_helper.c
> > @@ -249,13 +249,7 @@ static int drm_dp_dpcd_access(struct
> > drm_dp_aux *aux, u8 request,
> >   
> >   	mutex_lock(&aux->hw_mutex);
> >   
> > -	/*
> > -	 * The specification doesn't give any recommendation on how
> > often to
> > -	 * retry native transactions. We used to retry 7 times like for
> > -	 * aux i2c transactions but real world devices this wasn't
> > -	 * sufficient, bump to 32 which makes Dell 4k monitors happier.
> > -	 */
> > -	for (retry = 0; retry < 32; retry++) {
> > +	for (retry = 0; retry < aux->num_retries; retry++) {
> >   		if (ret != 0 && ret != -ETIMEDOUT) {
> >   			usleep_range(AUX_RETRY_INTERVAL,
> >   				     AUX_RETRY_INTERVAL + 100);
> > @@ -1744,6 +1738,8 @@ void drm_dp_aux_init(struct drm_dp_aux *aux)
> >   	aux->ddc.retries = 3;
> >   
> >   	aux->ddc.lock_ops = &drm_dp_i2c_lock_ops;
> > +	/*Still making the Dell 4k monitors happier*/
> 
> The original comment was helpful; this one isn't.

Noted and I apologize for the comment. Was just copy/past original
comment. 
> 

> Besides that, what problem does this patchset address? Too much
> probing? 

The problem mainly with disconnect. When disconnecting, AUX read will
fail because of timing out. The 32 retries cause the disconnect flow
especially for Type-C/TBT Docks with MST hubs taking a long time.
Just trying to reduce this disconnect time. In addition as I noted,
i915 does retry in addition to retries by this function. 

Currently this function retry for 4 AUX situations:
AUX_NAK, AUX_DEFER, I/O error reported by driver and AUX timeout.

> If I connect a Dell monitor to an Intel card, how often does it have
> to 
> probe?

I guess it depends on how you connect (direct, behind MST hub, behind DOCK with MST). But I believe the most time consuming is the disconnect flow. 

Thanks
Khaled
> 
> Best regards
> Thomas
> 
> > +	aux->num_retries = 32;
> >   }
> >   EXPORT_SYMBOL(drm_dp_aux_init);
> >   
> > diff --git a/include/drm/drm_dp_helper.h
> > b/include/drm/drm_dp_helper.h
> > index edffd1dcca3e..16cbfc8f5e66 100644
> > --- a/include/drm/drm_dp_helper.h
> > +++ b/include/drm/drm_dp_helper.h
> > @@ -1876,6 +1876,7 @@ struct drm_dp_aux {
> >   	struct mutex hw_mutex;
> >   	struct work_struct crc_work;
> >   	u8 crc_count;
> > +	int num_retries;
> >   	ssize_t (*transfer)(struct drm_dp_aux *aux,
> >   			    struct drm_dp_aux_msg *msg);
> >   	/**
> > 
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2021-02-10 10:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-10  8:33 [Intel-gfx] [RFC PATCH 1/2] drm/dp: Make number of AUX retries configurable by display drivers Khaled Almahallawy
2021-02-10  8:33 ` [Intel-gfx] [RFC PATCH 2/2] drm/i915/dp: Retry AUX requests 7 times Khaled Almahallawy
2021-02-10  8:54 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [RFC,1/2] drm/dp: Make number of AUX retries configurable by display drivers Patchwork
2021-02-10  8:55 ` [Intel-gfx] [RFC PATCH 1/2] " Thomas Zimmermann
2021-02-10 10:16   ` Almahallawy, Khaled [this message]
2021-02-10  8:57 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [RFC,1/2] " Patchwork
2021-02-10  9:25 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2021-02-10 18:03 ` [Intel-gfx] [RFC PATCH 1/2] " Lyude Paul
2021-02-11  6:56   ` Almahallawy, Khaled
2021-02-12  0:51     ` Lyude Paul
2021-02-13  2:01     ` Lyude Paul
2021-02-13 10:26       ` Almahallawy, Khaled
2021-02-16 19:06         ` Lyude Paul

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=a24dffd636a8999fd2eeedb04ceb813906d711e3.camel@intel.com \
    --to=khaled.almahallawy@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=seanpaul@chromium.org \
    --cc=tzimmermann@suse.de \
    /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