Mika Westerberg 04a8e39c8c thunderbolt: Use different lane for second DisplayPort tunnel ... [ Upstream commit 9d2d0a5cf0 ] Brad reported that on Apple hardware with Light Ridge or Falcon Ridge controller, plugging in a chain of Thunderbolt displays (Light Ridge based controllers) causes all kinds of tearing and flickering. The reason for this is that on Thunderbolt 1 hardware there is no lane bonding so we have two independent 10 Gb/s lanes, and currently Linux tunnels both displays through the lane 1. This makes the displays to share the 10 Gb/s bandwidth which may not be enough for higher resolutions. For this reason make the second tunnel go through the lane 0 instead. This seems to match what the macOS connection manager is also doing. Reported-by: Brad Campbell <lists2009@fnarfbargle.com> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com> Tested-by: Brad Campbell <lists2009@fnarfbargle.com> Signed-off-by: Sasha Levin <sashal@kernel.org>		2022-06-14 18:36:20 +02:00
..
acpi.c	thunderbolt: Runtime PM activate both ends of the device link	2022-01-27 11:04:36 +01:00
cap.c
ctl.c
ctl.h
debugfs.c
dma_port.c
dma_port.h
dma_test.c
domain.c
eeprom.c
icm.c
Kconfig
lc.c
Makefile
nhi.c
nhi.h
nhi_ops.c
nhi_regs.h
nvm.c
path.c
property.c
quirks.c
retimer.c
sb_regs.h
switch.c
tb.c	thunderbolt: Use different lane for second DisplayPort tunnel	2022-06-14 18:36:20 +02:00
tb.h
tb_msgs.h
tb_regs.h
test.c	thunderbolt: Use different lane for second DisplayPort tunnel	2022-06-14 18:36:20 +02:00
tmu.c
tunnel.c	thunderbolt: Use different lane for second DisplayPort tunnel	2022-06-14 18:36:20 +02:00
tunnel.h	thunderbolt: Use different lane for second DisplayPort tunnel	2022-06-14 18:36:20 +02:00
usb4.c
usb4_port.c
xdomain.c