From: "Shankar, Uma" <uma.shankar@intel.com>
To: "Murthy, Arun R" <arun.r.murthy@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Cc: "tprevite@gmail.com" <tprevite@gmail.com>,
"Nikula, Jani" <jani.nikula@intel.com>,
"Zanoni, Paulo R" <paulo.r.zanoni@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/dp: wait on timeout before retry
Date: Mon, 4 Jul 2022 12:27:36 +0000 [thread overview]
Message-ID: <248516b5125c4a109497bfe7ad506da4@intel.com> (raw)
In-Reply-To: <20220704072352.1331682-1-arun.r.murthy@intel.com>
> -----Original Message-----
> From: Murthy, Arun R <arun.r.murthy@intel.com>
> Sent: Monday, July 4, 2022 12:54 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: ville.syrjala@linux.intel.com; Zanoni, Paulo R <paulo.r.zanoni@intel.com>;
> tprevite@gmail.com; Shankar, Uma <uma.shankar@intel.com>; Nikula, Jani
> <jani.nikula@intel.com>; Murthy, Arun R <arun.r.murthy@intel.com>
> Subject: [PATCH] drm/i915/dp: wait on timeout before retry
>
> On linktraining error/timeout before retry need to wait for 400usec as per the DP
> CTS spec1.2 Under section 2.7.2 AUX Transaction Response/Reply Time-outs AUX
> Replier (the uPacket RX) must start sending the reply back to the AUX requester (the
> uPacket TX) within the response period of 300μs. The timer for Response Time-out
> starts ticking after the uPacket RX has finished receiving the AUX STOP condition
> which ends the AUX Request transaction.
> The timer is reset either when the Response Time-out period has elapsed or when
> the uPacket RX has started to send the AUX Sync pattern (which follows
> 10 to 16 active pre-charge pulses) for the Reply transaction. If the uPacket TX does
> not receive a reply from the uPacket RX it must wait for a Reply Time-out period of
> 400us before initiating the next AUX Request transaction. The timer for the Reply
> Time-out starts ticking after the uPacket TX has finished sending the AUX STOP
> condition.
>
> The patch with commit 74ebf294a1dd ("drm/i915: Add a delay in Displayport AUX
> transactions for compliance testing") removes this delay mentioning the hardware
> already meets this requirement, but as per the spec the delay mentioned in the spec
> specifies how long to wait for the receiver response before timeout. So the delay
> here to wait for timeout and not a delay after timeout. The DP spec specifies a delay
> after timeout and hence adding this delay.
>
> v2: fixed checkpatch warning and error
> v3: used proper indentation
> v4: added DP CEA 1.2 spec details in patch commit msg
Looks Good to me.
Reviewed-by: Uma Shankar <uma.shankar@intel.com>
> Signed-off-by: Arun R Murthy <arun.r.murthy@intel.com>
> Acked-by: Jani Nikula <jani.nikula@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_dp_aux.c | 8 ++------
> 1 file changed, 2 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dp_aux.c
> b/drivers/gpu/drm/i915/display/intel_dp_aux.c
> index 2bc119374555..722c9f210690 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp_aux.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp_aux.c
> @@ -286,13 +286,9 @@ intel_dp_aux_xfer(struct intel_dp *intel_dp,
> /*
> * DP CTS 1.2 Core Rev 1.1, 4.2.1.1 & 4.2.1.2
> * 400us delay required for errors and timeouts
> - * Timeout errors from the HW already meet this
> - * requirement so skip to next iteration
> */
> - if (status & DP_AUX_CH_CTL_TIME_OUT_ERROR)
> - continue;
> -
> - if (status & DP_AUX_CH_CTL_RECEIVE_ERROR) {
> + if (status & (DP_AUX_CH_CTL_RECEIVE_ERROR |
> + DP_AUX_CH_CTL_TIME_OUT_ERROR)) {
> usleep_range(400, 500);
> continue;
> }
> --
> 2.25.1
next prev parent reply other threads:[~2022-07-04 16:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 10:59 [Intel-gfx] [PATCH] drm/i915/dp: wait on timeout before retry Arun R Murthy
2022-06-28 2:01 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2022-06-28 2:21 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-06-28 15:49 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-07-01 10:11 ` [Intel-gfx] [PATCH] " Jani Nikula
2022-07-01 10:24 ` Murthy, Arun R
2022-07-01 10:48 ` [Intel-gfx] [PATCHv2] " Arun R Murthy
2022-07-01 10:54 ` Jani Nikula
2022-07-01 11:03 ` [Intel-gfx] [PATCHv3] " Arun R Murthy
2022-07-01 11:14 ` Jani Nikula
2022-07-04 5:24 ` Shankar, Uma
2022-07-04 5:37 ` Murthy, Arun R
2022-07-04 6:31 ` Shankar, Uma
2022-07-01 11:35 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/dp: wait on timeout before retry (rev2) Patchwork
2022-07-01 12:07 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/dp: wait on timeout before retry (rev3) Patchwork
2022-07-02 4:11 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-07-04 7:23 ` [Intel-gfx] [PATCH] drm/i915/dp: wait on timeout before retry Arun R Murthy
2022-07-04 12:27 ` Shankar, Uma [this message]
2022-07-04 14:11 ` Ville Syrjälä
2022-07-04 16:01 ` Murthy, Arun R
2022-07-26 17:04 ` Imre Deak
2022-07-18 11:18 ` Murthy, Arun R
2022-07-19 8:12 ` Shankar, Uma
2022-07-04 18:54 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/dp: wait on timeout before retry (rev4) Patchwork
2022-07-04 22:49 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
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=248516b5125c4a109497bfe7ad506da4@intel.com \
--to=uma.shankar@intel.com \
--cc=arun.r.murthy@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=paulo.r.zanoni@intel.com \
--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 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.