Lines Matching refs:tunnels
24 * @tunnel_list: List of active tunnels
102 * Find all DP tunnels that go through all the same USB4 links
103 * as this one. Because we always setup tunnels the same way we
104 * can just check for the routers at both ends of the tunnels
655 * Find all DP tunnels that cross the port and reduce
948 * tunnels and know which switches were authorized already by
1002 * Create USB 3.x tunnels only when the switch is plugged to the
1004 * and want to discover existing USB 3.x tunnels before we create
1056 * PCIe and DMA tunnels do not consume guaranteed
1066 * tb_free_invalid_tunnels() - destroy tunnels of devices that have gone away
1182 * tunnels under the host router USB4 port, even
1473 * Tear down all DP tunnels and release their resources. They
1721 * all the tunnels below.
1842 * the reservation of the tunnel. Since all the tunnels
1845 * account for the other tunnels automatically below.
1860 * Then go over all tunnels that cross the same USB4 ports (they
2051 /* tunnels are only present after everything has been initialized */
2054 * DMA tunnels require the driver to be functional so we
2055 * tear them down. Other protocol tunnels can be left
2130 /* Find out tunnels created by the boot firmware */
2132 /* Add DP resources from the DP tunnels created by the boot firmware */
2135 * If the boot firmware did not create USB 3.x tunnels create them
2199 LIST_HEAD(tunnels);
2213 * restore kernel might have created tunnels of its own. Since
2217 tb_switch_discover_tunnels(tb->root_switch, &tunnels, false);
2218 list_for_each_entry_safe_reverse(tunnel, n, &tunnels, list) {
2225 /* Re-create our tunnels now */
2240 tb_dbg(tb, "tunnels restarted, sleeping for 100ms\n");
2368 * tunnels are lost. The NHI driver will try to reestablish all tunnels
2405 * back to NHI so that PCIe tunnels can be re-established after
2459 * Device links are needed to make sure we establish tunnels