✓ CI.checkpatch: success for drm/dp: Rework LTTPR transparent mode handling and add support to msm driver (rev3)

[Patchwork]

== Series Details ==

Series: drm/dp: Rework LTTPR transparent mode handling and add support to msm driver (rev3)
URL   : https://patchwork.freedesktop.org/series/140802/
State : success

== Summary ==

+ KERNEL=/kernel
+ git clone https://gitlab.freedesktop.org/drm/maintainer-tools mt
Cloning into 'mt'...
warning: redirecting to https://gitlab.freedesktop.org/drm/maintainer-tools.git/
+ git -C mt rev-list -n1 origin/master
30ab6715fc09baee6cc14cb3c89ad8858688d474
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 1c03f154897f9f383e3838d4b8712cdd509d74d9
Author: Abel Vesa <abel.vesa at linaro.org>
Date:   Fri Jan 3 14:58:18 2025 +0200

    drm/msm/dp: Add support for LTTPR handling
    
    Link Training Tunable PHY Repeaters (LTTPRs) are defined in DisplayPort
    1.4a specification. As the name suggests, these PHY repeaters are
    capable of adjusting their output for link training purposes.
    
    According to the DisplayPort standard, LTTPRs have two operating
    modes:
     - non-transparent - it replies to DPCD LTTPR field specific AUX
       requests, while passes through all other AUX requests
     - transparent - it passes through all AUX requests.
    
    Switching between this two modes is done by the DPTX by issuing
    an AUX write to the DPCD PHY_REPEATER_MODE register.
    
    The msm DP driver is currently lacking any handling of LTTPRs.
    This means that if at least one LTTPR is found between DPTX and DPRX,
    the link training would fail if that LTTPR was not already configured
    in transparent mode.
    
    The section 3.6.6.1 from the DisplayPort v2.0 specification mandates
    that before link training with the LTTPR is started, the DPTX may place
    the LTTPR in non-transparent mode by first switching to transparent mode
    and then to non-transparent mode. This operation seems to be needed only
    on first link training and doesn't need to be done again until device is
    unplugged.
    
    It has been observed on a few X Elite-based platforms which have
    such LTTPRs in their board design that the DPTX needs to follow the
    procedure described above in order for the link training to be successful.
    
    So add support for reading the LTTPR DPCD caps to figure out the number
    of such LTTPRs first. Then, for platforms (or Type-C dongles) that have
    at least one such an LTTPR, set its operation mode to transparent mode
    first and then to non-transparent, just like the mentioned section of
    the specification mandates.
    
    Tested-by: Johan Hovold <johan+linaro at kernel.org>
    Signed-off-by: Abel Vesa <abel.vesa at linaro.org>
+ /mt/dim checkpatch 901262fb6987b4fa0dbb26979a6c4e25f0ba8fd2 drm-intel
fe979726d520 drm/dp: Add helper to set LTTPRs in transparent mode
7254aa4bdbac drm/nouveau/dp: Use the generic helper to control LTTPR transparent mode
70ab5ea8d82a drm/i915/dp: Use the generic helper to control LTTPR transparent mode
1c03f154897f drm/msm/dp: Add support for LTTPR handling