Hi all, This series improves bandwidth allocation mode support to follow the USB4 spec more closely. In addition to that DisplayPort tunneling is made more robust so that if a tunnel does not come up properly (for example on a discrete controller the DisplayPort source from the graphics is not connected to the DisplayPort sink of the controller) we tear it down and continue pairing. This series improves bandwidth allocation mode support and DisplayPort tunneling to follow the USB4 spec more closely. Gil Fine (2): thunderbolt: Calculate DisplayPort tunnel bandwidth after DPRX capabilities read thunderbolt: Improve DisplayPort tunnel setup process to be more robust Mika Westerberg (8): thunderbolt: Use DP_LOCAL_CAP for maximum bandwidth calculation thunderbolt: Re-calculate estimated bandwidth when allocation mode is enabled thunderbolt: Handle bandwidth allocation mode disable request thunderbolt: Log an error if DPTX request is not cleared thunderbolt: Fail the failed bandwidth request properly thunderbolt: Re-order bandwidth group functions thunderbolt: Introduce tb_tunnel_direction_downstream() thunderbolt: Reserve released DisplayPort bandwidth for a group for 10 seconds drivers/thunderbolt/domain.c | 4 + drivers/thunderbolt/tb.c | 898 +++++++++++++++++++++-------------- drivers/thunderbolt/tb.h | 10 + drivers/thunderbolt/tunnel.c | 96 ++-- drivers/thunderbolt/tunnel.h | 6 + drivers/thunderbolt/usb4.c | 4 +- 6 files changed, 596 insertions(+), 422 deletions(-) -- 2.43.0
