thunderbolt: Log which connection manager implementation is used

This makes it easier to figure out whether the driver is using firmware
or software based connection manager implementation.

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

diff --git a/drivers/thunderbolt/icm.c b/drivers/thunderbolt/icm.c
index 03e86817afc7a2dbb5670c70a62a5acf708600bd..beee6e6b8b6e6721ee62876d4fcbcb22d288e061 100644 (file)
--- a/drivers/thunderbolt/icm.c
+++ b/drivers/thunderbolt/icm.c
@@ -2302,5 +2302,7 @@ struct tb *icm_probe(struct tb_nhi *nhi)
                return NULL;
        }
 
+       tb_dbg(tb, "using firmware connection manager\n");
+
        return tb;
 }

diff --git a/drivers/thunderbolt/tb.c b/drivers/thunderbolt/tb.c
index 214fbc92c1b7d8333bddd3e2a1bc5d0e15b3bad6..51d5b031cada53bbfe627e03cc8106d19ef2bc99 100644 (file)
--- a/drivers/thunderbolt/tb.c
+++ b/drivers/thunderbolt/tb.c
@@ -1534,5 +1534,7 @@ struct tb *tb_probe(struct tb_nhi *nhi)
        INIT_LIST_HEAD(&tcm->dp_resources);
        INIT_DELAYED_WORK(&tcm->remove_work, tb_remove_work);
 
+       tb_dbg(tb, "using software connection manager\n");
+
        return tb;
 }