kernel/git/stable/linux-stable.git/drivers/thunderbolt/switch.c, branch linux-5.19.y

thunderbolt: Explicitly enable lane adapter hotplug events at startup

2022-10-24T07:56:58+00:00

commit 5d2569cb4a65c373896ec0217febdf88739ed295 upstream. Software that has run before the USB4 CM in Linux runs may have disabled hotplug events for a given lane adapter. Other CMs such as that one distributed with Windows 11 will enable hotplug events. Do the same thing in the Linux CM which fixes hotplug events on "AMD Pink Sardine". Cc: stable@vger.kernel.org Signed-off-by: Mario Limonciello Signed-off-by: Mika Westerberg Signed-off-by: Greg Kroah-Hartman

thunderbolt: Explicitly reset plug events delay back to USB4 spec value

2022-10-05T08:40:42+00:00

commit 31f87f705b3c1635345d8e8a493697099b43e508 upstream. If any software has interacted with the USB4 registers before the Linux USB4 CM runs, it may have modified the plug events delay. It has been observed that if this value too large, it's possible that hotplugged devices will negotiate a fallback mode instead in Linux. To prevent this, explicitly align the plug events delay with the USB4 spec value of 10ms. Cc: stable@vger.kernel.org Signed-off-by: Mario Limonciello Signed-off-by: Mika Westerberg Signed-off-by: Greg Kroah-Hartman

thunderbolt: Check router generation before connecting xHCI

2022-09-08T09:24:04+00:00

commit 93a3c0d4e8bfbb15145e5dd7da68a3de4b904aba upstream. Only Thunderbolt 3 routers need the xHCI connection flow. This also ensures the router actually has both lane adapters (1 and 3). While there move declaration of the boolean variables inside the block where they are being used. Fixes: 30a4eca69b76 ("thunderbolt: Add internal xHCI connect flows for Thunderbolt 3 devices") Cc: stable@vger.kernel.org Signed-off-by: Mika Westerberg Signed-off-by: Greg Kroah-Hartman

thunderbolt: Ignore port locked error in tb_port_wait_for_link_width()

2022-05-05T06:25:16+00:00

Sometimes when polling for the port after target link width is changed we get back port locked notification (because the link actually was reset and then re-trained). Instead of bailing out we can ignore these when polling for the width change as this is expected. Signed-off-by: Mika Westerberg

thunderbolt: Split setting link width and lane bonding into own functions

2022-05-05T06:25:04+00:00

When bonding lanes over XDomain the host that has "higher" UUID triggers link re-train for bonding, and the host that has "lower" UUID just waits for this to happen. To support this split setting the link width and triggering the actual bonding a separate functions that can be called as needed. While there remove duplicated empty line in the kernel-doc comment of tb_port_lane_bonding_disable(). Signed-off-by: Mika Westerberg

thunderbolt: Add debug logging when lane is enabled/disabled

2022-05-05T06:24:49+00:00

This is useful when debugging possible issues. Signed-off-by: Mika Westerberg

thunderbolt: Do not make DROM read success compulsory

2022-03-04T14:10:36+00:00

The USB4 specification doesn't make any requirements that reading a device router's DROM is needed for the operation of the device. Other connection manager solutions don't necessarily read it or gate the usability of the device on whether it was read. So make failures when reading the DROM show warnings but not fail the initialization of the router. Signed-off-by: Mario Limonciello Signed-off-by: Mika Westerberg

thunderbolt: Do not resume routers if UID is not set

2022-03-04T14:10:36+00:00

Routers might not have a UID set if the DROM read failed during initialization previously. Normally upon resume the UID is re-read to confirm it's the same device connected. * If the DROM read failed during init but then succeeded during resume it could either be a new device or faulty device * If the DROM read failed during init and also failed during resume it might be a different device plugged in all together. Detect this situation and prevent re-using the same configuration in these cirucmstances. Signed-off-by: Mario Limonciello Signed-off-by: Mika Westerberg

thunderbolt: Add internal xHCI connect flows for Thunderbolt 3 devices

2022-02-02T10:56:51+00:00

Both Alpine Ridge and Titan Ridge require special flows in order to activate the internal xHCI controller when there is USB device connected to the downstream type-C port. This implements the missing flows for both. Signed-off-by: Mika Westerberg

thunderbolt: Add module parameter for CLx disabling

2021-12-28T07:43:56+00:00

Add a module parameter that allows user to completely disable CLx functionality in case problems are found. Signed-off-by: Gil Fine Signed-off-by: Mika Westerberg