thunderbolt: Runtime resume USB4 port when retimers are scanned
authorMika Westerberg <mika.westerberg@linux.intel.com>
Mon, 15 Nov 2021 17:10:51 +0000 (19:10 +0200)
committerMika Westerberg <mika.westerberg@linux.intel.com>
Tue, 7 Dec 2021 12:18:33 +0000 (15:18 +0300)
commit1e56c88adecc2dfe14973fa47898861a839e62d4
treec4b4436c4716010370399dfaec1c67dead691e76
parent43bddb26e20af916249b5318200cfe1734c1700c
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>
drivers/thunderbolt/retimer.c