thunderbolt: Do not tear down tunnels when driver is unloaded
Now that we have capability to discover existing tunnels during driver load there is no point tearing down tunnels when the driver gets unloaded. Instead we can just leave them running. If user disconnects devices while there is no Thunderbolt driver loaded, tunneled protocol hotplug happens and is handled by the corresponding driver (pciehp in case of PCIe tunnel, GFX driver in case of DP tunnel). Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
This commit is contained in:
@@ -475,7 +475,7 @@ err_free:
|
||||
* tb_tunnel_free() - free a tunnel
|
||||
* @tunnel: Tunnel to be freed
|
||||
*
|
||||
* The tunnel must have been deactivated.
|
||||
* Frees a tunnel. The tunnel does not need to be deactivated.
|
||||
*/
|
||||
void tb_tunnel_free(struct tb_tunnel *tunnel)
|
||||
{
|
||||
@@ -484,14 +484,6 @@ void tb_tunnel_free(struct tb_tunnel *tunnel)
|
||||
if (!tunnel)
|
||||
return;
|
||||
|
||||
for (i = 0; i < tunnel->npaths; i++) {
|
||||
if (tunnel->paths[i] && tunnel->paths[i]->activated) {
|
||||
tb_tunnel_WARN(tunnel,
|
||||
"trying to free an activated tunnel\n");
|
||||
return;
|
||||
}
|
||||
}
|
||||
|
||||
for (i = 0; i < tunnel->npaths; i++) {
|
||||
if (tunnel->paths[i])
|
||||
tb_path_free(tunnel->paths[i]);
|
||||
|
Reference in New Issue
Block a user