summaryrefslogtreecommitdiff
path: root/include/linux
diff options
context:
space:
mode:
authorImre Deak <imre.deak@intel.com>2026-05-22 19:05:11 +0300
committerImre Deak <imre.deak@intel.com>2026-05-25 15:07:22 +0300
commit47f6d0e09064c765326a4d96f30292bc2c2ee405 (patch)
treeaaf79a49bec8b82655b8218011705e32cc02c6d3 /include/linux
parent4f1cab2e4863d96ce13b8d94151f4848e38c3d5b (diff)
downloadlinux-47f6d0e09064c765326a4d96f30292bc2c2ee405.tar.xz
drm/i915/dp: Reset link params after a DPRX capability change
There is no reason to distinguish between DPRX capability changes signaled via a long HPD and via an RX_CAP_CHANGED HPD IRQ. Both cases result in reading out the DPRX capabilities and updating the corresponding sink and common capabilities cached in intel_dp, however only the long HPD resets the link training/recovery state and MST link probe parameters correspondingly. The link training/recovery state may contain reduced maximum link rate/lane count values left over from a previous link training failure. Based on the above after an RX_CAP_CHANGED increased the link rate, lane count parameters the maximum link rate/lane count in the link training/recovery state may remain below these, leaving the newly added valid configurations unavailable for subsequent modesets in an inconsistent way. Handle RX_CAP_CHANGED IRQs the same way as long HPDs and reset the link recovery state and MST link probe parameters in that case as well. v2: Set intel_dp::reset_link_params instead of using a helper for this. (Ville). Cc: Ville Syrjälä <ville.syrjala@linux.intel.com> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com> Signed-off-by: Imre Deak <imre.deak@intel.com> Link: https://patch.msgid.link/20260522160514.2628249-2-imre.deak@intel.com
Diffstat (limited to 'include/linux')
0 files changed, 0 insertions, 0 deletions