diff options
| author | Mika Westerberg <mika.westerberg@linux.intel.com> | 2024-01-26 15:55:55 +0200 |
|---|---|---|
| committer | Mika Westerberg <mika.westerberg@linux.intel.com> | 2024-02-26 09:12:12 +0200 |
| commit | a75e0684efe567ae5f6a8e91a8360c4c1773cf3a (patch) | |
| tree | 90242375d89ae4745eac9a83aeef5171d2618057 /drivers/char | |
| parent | b4734507ac55cc7ea1380e20e83f60fcd7031955 (diff) | |
| download | linux-a75e0684efe567ae5f6a8e91a8360c4c1773cf3a.tar.gz linux-a75e0684efe567ae5f6a8e91a8360c4c1773cf3a.tar.bz2 linux-a75e0684efe567ae5f6a8e91a8360c4c1773cf3a.zip | |
thunderbolt: Keep the domain powered when USB4 port is in redrive mode
If a DiplayPort cable is directly connected to the host routers USB4
port, there is no tunnel involved but the port is in "redrive" mode
meaning that it is re-driving the DisplayPort signals from its
DisplayPort source. In this case we need to keep the domain powered on
otherwise once the domain enters D3cold the connected monitor blanks
too.
Since this happens only on Intel Barlow Ridge add a quirk that takes
runtime PM reference if we detect that the USB4 port entered redrive
mode (and release it once it exits the mode).
Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Diffstat (limited to 'drivers/char')
0 files changed, 0 insertions, 0 deletions