Return-Path: Message-ID: <1349977154.19673.0.camel@aeonflux> Subject: Re: [RFC 1/6] Bluetooth: Add new l2cap_chan struct members for high speed channels From: Marcel Holtmann To: Mat Martineau Cc: Andrei Emeltchenko , linux-bluetooth@vger.kernel.org Date: Thu, 11 Oct 2012 19:39:14 +0200 In-Reply-To: References: <1349966905-32336-1-git-send-email-Andrei.Emeltchenko.news@gmail.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Sender: linux-bluetooth-owner@vger.kernel.org List-ID: 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 > > Signed-off-by: Andrei Emeltchenko > > --- > > 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