diff options
author | 2022-04-01 17:24:28 +0300 | |
---|---|---|
committer | 2022-04-19 10:26:18 +0300 | |
commit | 9d2d0a5cf0ca063f417681cc33e767ce52615286 (patch) | |
tree | a5f8c4deb919a2e471e8ba39290963f4717345cc /tools/perf/scripts/python/call-graph-from-sql.py | |
parent | thunderbolt: Dump path config space entries during discovery (diff) | |
download | linux-dev-9d2d0a5cf0ca063f417681cc33e767ce52615286.tar.xz linux-dev-9d2d0a5cf0ca063f417681cc33e767ce52615286.zip |
thunderbolt: Use different lane for second DisplayPort tunnel
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>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-sql.py')
0 files changed, 0 insertions, 0 deletions