Hi Mat, > > An L2CAP channel using high speed continues to be associated with a > > BR/EDR l2cap_conn, while also tracking an additional hci_conn > > (representing a physical link on a high speed controller) and hci_chan > > (representing a logical link). There may only be one physical link > > between two high speed controllers. Each physical link may contain > > several logical links, with each logical link representing a channel > > with specific quality of service. > > > > During a channel move, the destination channel id, current move state, > > and role (initiator vs. responder) are tracked and used by the channel > > move state machine. The ident value associated with a move request > > must also be stored in order to use it in later move responses. > > > > The active channel is stored in local_amp_id. > > > > Signed-off-by: Mat Martineau <mathewm@xxxxxxxxxxxxxx> > > Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@xxxxxxxxx> > > --- > > include/net/bluetooth/l2cap.h | 29 +++++++++++++++++++++++++++++ > > net/bluetooth/l2cap_core.c | 5 +++++ > > 2 files changed, 34 insertions(+) > > Did you have to do anything other than rebase these 6 patches? > > I can post a PATCHv1 set tomorrow or Monday. that would be great. I am trying to get a few free cycles to get this all reviewed and merged. So we finally get HS into upstream for larger exposure. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
