3cea8af2d1
Currently, when configuring TMU (Time Management Unit) mode of a given router, we take into account only its own TMU requirements ignoring other routers in the domain. This is problematic if the router we are configuring has lower TMU requirements than what is already configured in the domain. In the scenario below, we have a host router with two USB4 ports: A and B. Port A connected to device router #1 (which supports CL states) and existing DisplayPort tunnel, thus, the TMU mode is HiFi uni-directional. 1. Initial topology [Host] A/ / [Device #1] / Monitor 2. Plug in device #2 (that supports CL states) to downstream port B of the host router [Host] A/ B\ / \ [Device #1] [Device #2] / Monitor The TMU mode on port B and port A will be configured to LowRes which is not what we want and will cause monitor to start flickering. To address this we first scan the domain and search for any router configured to HiFi uni-directional mode, and if found, configure TMU mode of the given router to HiFi uni-directional as well. Cc: stable@vger.kernel.org Signed-off-by: Gil Fine <gil.fine@linux.intel.com> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com> |
||
---|---|---|
.. | ||
acpi.c | ||
cap.c | ||
clx.c | ||
ctl.c | ||
ctl.h | ||
debugfs.c | ||
dma_port.c | ||
dma_port.h | ||
dma_test.c | ||
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 | ||
trace.h | ||
tunnel.c | ||
tunnel.h | ||
usb4_port.c | ||
usb4.c | ||
xdomain.c |