Hi all, There has been ask if we can expose more details about the connected devices and the tunneling to userspace, so it can then provide more detailed information to the user. This series is not meant to be merged just yet but more like start of a discussion if the information here is enough or we perhaps want to do something differently. First we add uevent details for each device (USB4 router) that adds USB4_TYPE=host|device|hub and USB4_VERSION=1.0 (if the device actually is USB4). The host|device|hub definitions follow the USB4 spec. Then for each device router we expose two new attributes: "usb3" and "dp" that if present mean that the device has corresponding adapter (USB 3.x upstream adapter and DP OUT adapter). The contents of the attributes then hold number of tunnels ending to this router. So if USB 3.x is tunneled "usb3" reads 1. Since there can be multiple DP OUT adaptes the "dp" attribute holds number of DP tunnels ending to this router. For PCIe tunneling the "authorized" attribute works the same way. I'm including the folks who have been working on the userspace side of Thunderbolt in hope to get some feedback whether this is useful approach or perhaps there are better ideas. Thanks! Mika Westerberg (3): thunderbolt: Add details to router uevent thunderbolt: Hide authorized attribute if router does not support PCIe tunnels thunderbolt: Expose more details about USB 3.x and DisplayPort tunnels .../ABI/testing/sysfs-bus-thunderbolt | 26 ++++++ drivers/thunderbolt/domain.c | 10 +++ drivers/thunderbolt/switch.c | 90 ++++++++++++++++++- drivers/thunderbolt/tb.c | 49 +++++++--- drivers/thunderbolt/tb.h | 4 + include/linux/thunderbolt.h | 6 ++ 6 files changed, 173 insertions(+), 12 deletions(-) -- 2.30.1
