diff options
| author | Imre Deak <[email protected]> | 2022-04-08 22:46:29 +0000 |
|---|---|---|
| committer | Imre Deak <[email protected]> | 2022-04-27 06:52:40 +0000 |
| commit | eddbb074ce6a3af5fe1d9c546e5d474ca9fa799d (patch) | |
| tree | fa509c00c3aa24bae006bd82cb720052c50d696d /lib/debugobjects.c | |
| parent | Merge drm/drm-next into drm-intel-next (diff) | |
| download | kernel-eddbb074ce6a3af5fe1d9c546e5d474ca9fa799d.tar.gz kernel-eddbb074ce6a3af5fe1d9c546e5d474ca9fa799d.zip | |
drm/i915/dp: Add workaround for spurious AUX timeouts/hotplugs on LTTPR links
To avoid AUX timeouts and subsequent spurious hotplug interrupts, make
sure that the first DPCD access during detection is a read from an LTTPR
register.
Some ADLP DP link configuration at least with multiple LTTPRs expects
the first DPCD access during the LTTPR/DPCD detection after hotplug to
be a read from the LTTPR range starting with
DP_LT_TUNABLE_PHY_REPEATER_FIELD_DATA_STRUCTURE_REV. The side effect of
this read is to put each LTTPR into the LTTPR transparent or LTTPR
non-transparent mode.
The lack of the above read may leave some of the LTTPRs in non-LTTPR
mode, while other LTTPRs in LTTPR transparent or LTTPR non-transparent
mode (for instance LTTPRs after system suspend/resume that kept their
mode from before suspend). Due to the different AUX timeouts the
different modes imply, the DPCD access from a non-LTTPR range will
timeout and lead to an LTTPR generated hotplug towards the source (which
the LTTPR firmware uses to account for buggy TypeC adapters with a long
wake-up delay).
SYSCROS: 72939
v2: Keep DPCD read-out working on non-LTTPR platforms.
v3: Summarize what and why the patch does at the beginning of the commit
log. (Jani)
Signed-off-by: Imre Deak <[email protected]>
Reviewed-by: Jani Nikula <[email protected]>
Link: https://patchwork.freedesktop.org/patch/msgid/[email protected]
Diffstat (limited to 'lib/debugobjects.c')
0 files changed, 0 insertions, 0 deletions
