From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Srikanth V, NagaVenkata" <nagavenkata.srikanth.v@intel.com>,
"Kandpal, Suraj" <suraj.kandpal@intel.com>,
"Murthy, Arun R" <arun.r.murthy@intel.com>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Cc: "Murthy, Arun R" <arun.r.murthy@intel.com>
Subject: RE: [PATCH 3/3] drm/i915/dp: Include the time taken by AUX Tx for timeout
Date: Mon, 23 Sep 2024 14:45:44 +0300 [thread overview]
Message-ID: <87ldzi61av.fsf@intel.com> (raw)
In-Reply-To: <CH0PR11MB550828F237C40440851BA923C26F2@CH0PR11MB5508.namprd11.prod.outlook.com>
On Mon, 23 Sep 2024, "Srikanth V, NagaVenkata" <nagavenkata.srikanth.v@intel.com> wrote:
>> > -----Original Message-----
>> > From: Intel-xe <intel-xe-bounces@lists.freedesktop.org> On Behalf Of
>> > Arun R Murthy
>> > Sent: Thursday, September 12, 2024 10:36 AM
>> > To: intel-xe@lists.freedesktop.org; intel-gfx@lists.freedesktop.org
>> > Cc: Murthy, Arun R <arun.r.murthy@intel.com>; Srikanth V, NagaVenkata
>> > <nagavenkata.srikanth.v@intel.com>
>> > Subject: [PATCH 3/3] drm/i915/dp: Include the time taken by AUX Tx for
>> > timeout
>> >
>> > As per DP spec the timeout for LANE_CHANNEL_EQ_DONE is 400ms. But this
>>
>> Adding where in DP spec example dp2.1 section x.x is a good idea
>>
> Please refer to section 3.5.2.16.1 128b/132b DP LANEx_CHANNEL_EQ_DONE Sequnce
> and Figure3-51: 128b/132b DP EQ Time Budget Illustration of DP2.1a spec.
>
>> > timeout value is exclusively for the Aux RD Interval and excludes the
>> > time consumed for the AUX Tx (i.e reading/writing FFE presets). Add
>> > another 50ms for these AUX Tx to the 400ms timeout.
>>
>> Is this something we came up with by trial and error or is this also a part of spec
>>
> It's not by trail and erros. Timeout value of 450ms is part of DP.
It's a very poorly written spec, and contradicts itself. The only place
where I see 450 ms even mentioned is Figure 3-52. But everywhere else it
seems to say many times 400 ms is the max, without a hint that it would
be exclusive of aux. It does not say anything about the sum of rd
interval being related to the max of 400 ms either.
Regardless, I have no qualms about relaxing the timeout by 50 ms.
With the commit message explaining the above, with references,
Acked-by: Jani Nikula <jani.nikula@intel.com>
>
>> Regards,
>> Suraj Kandpal
>> >
>> > Signed-off-by: Srikanth V NagaVenkata
>> > <nagavenkata.srikanth.v@intel.com>
>> > Signed-off-by: Arun R Murthy <arun.r.murthy@intel.com>
>> > ---
>> > drivers/gpu/drm/i915/display/intel_dp_link_training.c | 2 +-
>> > 1 file changed, 1 insertion(+), 1 deletion(-)
>> >
>> > diff --git a/drivers/gpu/drm/i915/display/intel_dp_link_training.c
>> > b/drivers/gpu/drm/i915/display/intel_dp_link_training.c
>> > index ca179bed46ad..b6573934c6dd 100644
>> > --- a/drivers/gpu/drm/i915/display/intel_dp_link_training.c
>> > +++ b/drivers/gpu/drm/i915/display/intel_dp_link_training.c
>> > @@ -1414,7 +1414,7 @@ intel_dp_128b132b_lane_eq(struct intel_dp
>> > *intel_dp,
>> > }
>> >
>> > /* Time budget for the LANEx_EQ_DONE Sequence */
>> > - deadline = jiffies + msecs_to_jiffies_timeout(400);
>> > + deadline = jiffies + msecs_to_jiffies_timeout(450);
>> >
>> > for (try = 0; try < max_tries; try++) {
>> > fsleep(delay_us);
>> > --
>> > 2.25.1
>
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-09-23 11:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 5:05 [PATCH 0/3] Some correction in the DP Link Training dequence Arun R Murthy
2024-09-12 5:05 ` [PATCH 1/3] drm/i915/dp: use fsleep instead of usleep_rage for LT Arun R Murthy
2024-09-12 9:01 ` Jani Nikula
2024-09-12 10:04 ` Murthy, Arun R
2024-09-12 12:01 ` Srikanth V, NagaVenkata
2024-09-23 10:23 ` Jani Nikula
2024-09-12 9:05 ` Jani Nikula
2024-09-12 10:57 ` Murthy, Arun R
2024-09-23 10:32 ` Jani Nikula
2024-09-23 10:24 ` Jani Nikula
2024-09-23 12:59 ` Francois Dugast
2024-09-23 13:51 ` Jani Nikula
2024-09-12 5:05 ` [PATCH 2/3] drm/i915/dp: read Aux RD interval after reading the FFE preset Arun R Murthy
2024-09-12 9:04 ` Jani Nikula
2024-09-12 10:54 ` Murthy, Arun R
2024-09-12 11:58 ` Srikanth V, NagaVenkata
2024-09-23 6:21 ` Kandpal, Suraj
2024-09-23 6:28 ` Srikanth V, NagaVenkata
2024-09-23 6:32 ` Kandpal, Suraj
2024-09-23 6:56 ` Kandpal, Suraj
2024-09-24 5:58 ` Murthy, Arun R
2024-09-23 11:09 ` Jani Nikula
2024-09-24 6:00 ` Murthy, Arun R
2024-09-12 5:05 ` [PATCH 3/3] drm/i915/dp: Include the time taken by AUX Tx for timeout Arun R Murthy
2024-09-23 6:23 ` Kandpal, Suraj
2024-09-23 6:31 ` Srikanth V, NagaVenkata
2024-09-23 6:58 ` Kandpal, Suraj
2024-09-23 11:45 ` Jani Nikula [this message]
2024-09-12 6:12 ` ✓ Fi.CI.BAT: success for Some correction in the DP Link Training dequence Patchwork
2024-09-13 0:00 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-09-23 6:26 ` [PATCH 0/3] " Kandpal, Suraj
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=87ldzi61av.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=arun.r.murthy@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=nagavenkata.srikanth.v@intel.com \
--cc=suraj.kandpal@intel.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