summaryrefslogtreecommitdiffstats
path: root/drivers/thunderbolt
diff options
context:
space:
mode:
authorMika Westerberg <mika.westerberg@linux.intel.com>2020-11-10 11:02:31 +0300
committerMika Westerberg <mika.westerberg@linux.intel.com>2020-11-30 14:39:23 +0300
commite0258805d71b9e9febeae9d9ae39ae7997384b16 (patch)
tree1cb2e13c789e9079b81b7cfcf8e2131176592f43 /drivers/thunderbolt
parent45ef561abcdd6cbaba0ab391b60d1831d2ac47af (diff)
downloadlinux-e0258805d71b9e9febeae9d9ae39ae7997384b16.tar.bz2
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>
Diffstat (limited to 'drivers/thunderbolt')
-rw-r--r--drivers/thunderbolt/icm.c2
-rw-r--r--drivers/thunderbolt/tb.c2
2 files changed, 4 insertions, 0 deletions
diff --git a/drivers/thunderbolt/icm.c b/drivers/thunderbolt/icm.c
index 03e86817afc7..beee6e6b8b6e 100644
--- 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 214fbc92c1b7..51d5b031cada 100644
--- 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;
}