Zhan Liu 5948190a0e drm/amd/display: Reduce delay when sink device not able to ACK 00340h write ... [Why] Theoretically, per DP 1.4a spec, sink device needs to AUX_ACK 00340h write. However, due to hardware limitation, some sink devices have no 00340h dpcd address at all. This results in sink side fails to reply ACK, and consequently cause source side keep retrying DPCD write on DPCD 00340h. This results in significant delay when DPCD 00340h write is triggered (e.g. at S3 resume). [How] Check whether sink device could ACK on DPCD 00340h write on boot. If sink device fails to ACK, then remember that, so we won't write to DPCD 00340h later on. There will be a drm.debug KMS level message to inform user once a 00340h DPCD write is skipped on purpose. Reviewed-by: Nikola Cornij <Nikola.Cornij@amd.com> Acked-by: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com> Signed-off-by: Zhan Liu <zhan.liu@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>		2021-07-23 10:07:57 -04:00
..
drm	drm/amd/display: Reduce delay when sink device not able to ACK 00340h write	2021-07-23 10:07:57 -04:00
host1x	gpu: host1x: Split up client initalization and registration	2021-05-17 12:31:05 +02:00
ipu-v3	gpu: ipu-v3: Add Rec.709 limited range support to DP	2021-05-10 17:20:29 +02:00
trace
vga	vgaarb: Use ACPI HID name to find integrated GPU	2021-05-20 14:55:56 -04:00
Makefile