aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
diff options
context:
space:
mode:
authorMichael Strauss <[email protected]>2025-02-26 15:03:48 +0000
committerAlex Deucher <[email protected]>2025-06-18 17:03:29 +0000
commitd358a51444c88bcc995e471dc8cc840f19e4b374 (patch)
tree30d05c9d01cc187da2da3a74faafc98c48f90174 /drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
parentdrm/amd/display: Add dc cap for dp tunneling (diff)
downloadkernel-d358a51444c88bcc995e471dc8cc840f19e4b374.tar.gz
kernel-d358a51444c88bcc995e471dc8cc840f19e4b374.zip
drm/amd/display: Get LTTPR IEEE OUI/Device ID From Closest LTTPR To Host
[WHY] These fields are read for the explicit purpose of detecting embedded LTTPRs (i.e. between host ASIC and the user-facing port), and thus need to calculate the correct DPCD address offset based on LTTPR count to target the appropriate LTTPR's DPCD register space with these queries. [HOW] Cascaded LTTPRs in a link each snoop and increment LTTPR count when queried via DPCD read, so an LTTPR embedded in a source device (e.g. USB4 port on a laptop) will always be addressible using the max LTTPR count seen by the host. Therefore we simply need to use a recently added helper function to calculate the correct DPCD address to target potentially embedded LTTPRs based on the received LTTPR count. Cc: Mario Limonciello <[email protected]> Cc: Alex Deucher <[email protected]> Reviewed-by: Wenjing Liu <[email protected]> Signed-off-by: Michael Strauss <[email protected]> Signed-off-by: Alex Hung <[email protected]> Tested-by: Daniel Wheeler <[email protected]> Signed-off-by: Alex Deucher <[email protected]> (cherry picked from commit 791897f5c77a2a65d0e500be4743af2ddf6eb061) Cc: [email protected]
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_device.c')
0 files changed, 0 insertions, 0 deletions