diff options
author | Imre Deak <imre.deak@intel.com> | 2025-06-05 11:28:46 +0300 |
---|---|---|
committer | Imre Deak <imre.deak@intel.com> | 2025-06-12 20:41:49 +0300 |
commit | a40c5d727b8111b5db424a1e43e14a1dcce1e77f (patch) | |
tree | c5597e6ce81188cde08cebd3cf44f00b43721a86 /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | 9d4e26042c6094d4f1abc7a4e7f55e426641312b (diff) |
drm/dp: Change AUX DPCD probe address from DPCD_REV to LANE0_1_STATUS
Reading DPCD registers has side-effects in general. In particular
accessing registers outside of the link training register range
(0x102-0x106, 0x202-0x207, 0x200c-0x200f, 0x2216) is explicitly
forbidden by the DP v2.1 Standard, see
3.6.5.1 DPTX AUX Transaction Handling Mandates
3.6.7.4 128b/132b DP Link Layer LTTPR Link Training Mandates
Based on my tests, accessing the DPCD_REV register during the link
training of an UHBR TBT DP tunnel sink leads to link training failures.
Solve the above by using the DP_LANE0_1_STATUS (0x202) register for the
DPCD register access quirk.
Cc: <stable@vger.kernel.org>
Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Cc: Jani Nikula <jani.nikula@linux.intel.com>
Acked-by: Jani Nikula <jani.nikula@intel.com>
Signed-off-by: Imre Deak <imre.deak@intel.com>
Link: https://lore.kernel.org/r/20250605082850.65136-2-imre.deak@intel.com
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions