diff options
author | Mika Westerberg <mika.westerberg@linux.intel.com> | 2019-03-26 15:52:30 +0300 |
---|---|---|
committer | Mika Westerberg <mika.westerberg@linux.intel.com> | 2019-11-02 12:13:31 +0300 |
commit | 8afe909b78e16ee4baecf78fd4e404aabf425f8c (patch) | |
tree | 99323dee80fdda2733e71a9950e45d5b7464549e /Kbuild | |
parent | de718ac7b6aefa594d5d95881882bc68ec3b83b6 (diff) | |
download | linux-stable-8afe909b78e16ee4baecf78fd4e404aabf425f8c.tar.gz linux-stable-8afe909b78e16ee4baecf78fd4e404aabf425f8c.tar.bz2 linux-stable-8afe909b78e16ee4baecf78fd4e404aabf425f8c.zip |
thunderbolt: Add Display Port adapter pairing and resource management
To perform proper Display Port tunneling for Thunderbolt 3 devices we
need to allocate DP resources for DP IN port before they can be used.
The reason for this is that the user can also connect a monitor directly
to the Type-C ports in which case the Thunderbolt controller acts as
re-driver for Display Port (no tunneling takes place) taking the DP
sinks away from the connection manager. This allocation is done using
special sink allocation registers available through the link controller.
We can pair DP IN to DP OUT only if
* DP IN has sink allocated via link controller
* DP OUT port receives hotplug event
For DP IN adapters (only for the host router) we first query whether
there is DP resource available (it may be the previous instance of the
driver for example already allocated it) and if it is we add it to the
list. We then update the list when after each plug/unplug event to a DP
IN/OUT adapter. Each time the list is updated we try to find additional
DP IN <-> DP OUT pairs for tunnel establishment. This strategy also
makes it possible to establish another tunnel in case there are 3
monitors connected and one gets unplugged releasing the DP IN adapter
for the new tunnel.
Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Diffstat (limited to 'Kbuild')
0 files changed, 0 insertions, 0 deletions