thunderbolt: Do not re-establish XDomain DMA paths automatically

This step is actually not needed. The service drivers themselves will
handle this once they have negotiated the service up and running again
with the remote side. Also dropping this makes it easier to add support
for multiple DMA tunnels over a single XDomain connection.

Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>

diff --git a/drivers/thunderbolt/xdomain.c b/drivers/thunderbolt/xdomain.c
index 584bb5e..a165766 100644 (file)
--- a/drivers/thunderbolt/xdomain.c
+++ b/drivers/thunderbolt/xdomain.c
@@ -946,19 +946,6 @@ static int populate_properties(struct tb_xdomain *xd,
        return 0;
 }
 
-/* Called with @xd->lock held */
-static void tb_xdomain_restore_paths(struct tb_xdomain *xd)
-{
-       if (!xd->resume)
-               return;
-
-       xd->resume = false;
-       if (xd->transmit_path) {
-               dev_dbg(&xd->dev, "re-establishing DMA path\n");
-               tb_domain_approve_xdomain_paths(xd->tb, xd);
-       }
-}
-
 static inline struct tb_switch *tb_xdomain_parent(struct tb_xdomain *xd)
 {
        return tb_to_switch(xd->dev.parent);
@@ -1084,16 +1071,8 @@ static void tb_xdomain_get_properties(struct work_struct *work)
        mutex_lock(&xd->lock);
 
        /* Only accept newer generation properties */
-       if (xd->properties && gen <= xd->property_block_gen) {
-               /*
-                * On resume it is likely that the properties block is
-                * not changed (unless the other end added or removed
-                * services). However, we need to make sure the existing
-                * DMA paths are restored properly.
-                */
-               tb_xdomain_restore_paths(xd);
+       if (xd->properties && gen <= xd->property_block_gen)
                goto err_free_block;
-       }
 
        dir = tb_property_parse_dir(block, ret);
        if (!dir) {
@@ -1118,8 +1097,6 @@ static void tb_xdomain_get_properties(struct work_struct *work)
 
        tb_xdomain_update_link_attributes(xd);
 
-       tb_xdomain_restore_paths(xd);
-
        mutex_unlock(&xd->lock);
 
        kfree(block);
@@ -1332,15 +1309,7 @@ static int __maybe_unused tb_xdomain_suspend(struct device *dev)
 
 static int __maybe_unused tb_xdomain_resume(struct device *dev)
 {
-       struct tb_xdomain *xd = tb_to_xdomain(dev);
-
-       /*
-        * Ask tb_xdomain_get_properties() restore any existing DMA
-        * paths after properties are re-read.
-        */
-       xd->resume = true;
-       start_handshake(xd);
-
+       start_handshake(tb_to_xdomain(dev));
        return 0;
 }
 

diff --git a/include/linux/thunderbolt.h b/include/linux/thunderbolt.h
index 659a0a8..7ec9771 100644 (file)
--- a/include/linux/thunderbolt.h
+++ b/include/linux/thunderbolt.h
@@ -185,7 +185,6 @@ void tb_unregister_property_dir(const char *key, struct tb_property_dir *dir);
  * @link_speed: Speed of the link in Gb/s
  * @link_width: Width of the link (1 or 2)
  * @is_unplugged: The XDomain is unplugged
- * @resume: The XDomain is being resumed
  * @needs_uuid: If the XDomain does not have @remote_uuid it will be
  *             queried first
  * @transmit_path: HopID which the remote end expects us to transmit
@@ -231,7 +230,6 @@ struct tb_xdomain {
        unsigned int link_speed;
        unsigned int link_width;
        bool is_unplugged;
-       bool resume;
        bool needs_uuid;
        u16 transmit_path;
        u16 transmit_ring;