Mika Westerberg c1976a4248 thunderbolt: Runtime PM activate both ends of the device link ... [ Upstream commit f3380cac0c0b3a6f49ab161e2a057c363962f48d ] If protocol tunnels are already up when the driver is loaded, for instance if the boot firmware implements connection manager of its own, runtime PM reference count of the consumer devices behind the tunnel might have been increased already before the device link is created but the supplier device runtime PM reference count is not. This leads to a situation where the supplier (the Thunderbolt driver) can runtime suspend even if it should not because the corresponding protocol tunnel needs to be up causing the devices to be removed from the corresponding native bus. Prevent this from happening by making both sides of the link runtime PM active briefly. The pm_runtime_put() for the consumer (PCIe root/downstream port, xHCI) then allows it to runtime suspend again but keeps the supplier runtime resumed the whole time it is runtime active. Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com> Reviewed-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Signed-off-by: Sasha Levin <sashal@kernel.org>		2022-01-27 10:54:14 +01:00
..
acpi.c	thunderbolt: Runtime PM activate both ends of the device link	2022-01-27 10:54:14 +01:00
cap.c
ctl.c
ctl.h
debugfs.c
dma_port.c
dma_port.h
domain.c
eeprom.c
icm.c
Kconfig
lc.c
Makefile
nhi_ops.c
nhi_regs.h
nhi.c
nhi.h
nvm.c
path.c
property.c
quirks.c
retimer.c
sb_regs.h
switch.c
tb_msgs.h
tb_regs.h
tb.c
tb.h
test.c
tmu.c
tunnel.c
tunnel.h
usb4.c
xdomain.c