On Fri, Jan 20, 2023 at 12:19:18PM +0100, Christian Schaubschläger wrote: > Hi, > >> You're right! With this commit reverted it uses the software connection manager, with the commit applied it uses the firmware connection manager. > > Hmm, so reverting this commit enables software connection manager and > > makes the Lenovo system work? Are you sure? that's completely opposite > > how the HP system behaves ;-) > > No, with the software CM active it does _not_ work! The patch > introduced in 5.18.11 somehow prevents the software CM to be used... > > 5.18.9, without the comit: > > bash-5.0# uname -r > 5.18.9-superschaf-uefi-bisect > bash-5.0# dmesg |grep manager > [ 2.028144] thunderbolt 0000:00:0d.2: using software connection manager > [ 2.220380] thunderbolt 0000:00:0d.3: using software connection manager > > and 5.18.11, including the commit: > > bash-5.0# uname -r > 5.18.11-superschaf-uefi-bisect > bash-5.0# dmesg | grep manager > [ 1.827993] thunderbolt 0000:00:0d.2: using firmware connection manager > [ 2.113706] thunderbolt 0000:00:0d.3: using firmware connection manager > > On the HP the software CM is used always (unless I run a kernel with CONFIG_USB4=n). Okay then it is consistent. Thanks for confirming.
