diff options
| author | Mika Westerberg <mika.westerberg@linux.intel.com> | 2021-11-15 19:10:51 +0200 |
|---|---|---|
| committer | Mika Westerberg <mika.westerberg@linux.intel.com> | 2021-12-07 15:18:33 +0300 |
| commit | 1e56c88adecc2dfe14973fa47898861a839e62d4 (patch) | |
| tree | c4b4436c4716010370399dfaec1c67dead691e76 /scripts/generate_rust_analyzer.py | |
| parent | 43bddb26e20af916249b5318200cfe1734c1700c (diff) | |
thunderbolt: Runtime resume USB4 port when retimers are scanned
Sometimes when plugging in a USB4 device we might see following error:
thunderbolt 1-0:3.1: runtime PM trying to activate child device 1-0:3.1 but parent (usb4_port3) is not active
This happens because the parent USB4 port was still runtime suspended.
Fix this by runtime resuming the USB4 port before scanning the retimers
below it.
Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions