From: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
To: Mat Martineau <mathewm@codeaurora.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [RFC 1/6] Bluetooth: Add new l2cap_chan struct members for high speed channels
Date: Fri, 12 Oct 2012 10:25:15 +0300 [thread overview]
Message-ID: <20121012072513.GB28051@aemeltch-MOBL1> (raw)
In-Reply-To: <alpine.DEB.2.02.1210110858010.26189@mathewm-linux>
Hi Mat,
On Thu, Oct 11, 2012 at 08:58:40AM -0700, Mat Martineau wrote:
>
> Andrei -
>
> On Thu, 11 Oct 2012, Andrei Emeltchenko wrote:
>
> >From: Mat Martineau <mathewm@codeaurora.org>
> >
> >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@codeaurora.org>
> >Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
> >---
> >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 would wish to, but I am stuck with dependencies :(
At least I need chan pointers to hs_hchan and hs_hcon ...
Best regards
Andrei Emeltchenko
> I can post a PATCHv1 set tomorrow or Monday.
This sounds good. I will also send my patches later today.
Best regards
Andrei Emeltchenko
prev parent reply other threads:[~2012-10-12 7:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 14:48 [RFC 1/6] Bluetooth: Add new l2cap_chan struct members for high speed channels Andrei Emeltchenko
2012-10-11 14:48 ` [RFC 2/6] Bluetooth: Process create response and connect response identically Andrei Emeltchenko
2012-10-11 15:09 ` Marcel Holtmann
2012-10-12 9:46 ` Gustavo Padovan
2012-10-11 14:48 ` [RFC 3/6] Bluetooth: Factor out common L2CAP connection code Andrei Emeltchenko
2012-10-11 15:11 ` Marcel Holtmann
2012-10-12 9:50 ` Gustavo Padovan
2012-10-11 14:48 ` [RFC 4/6] Bluetooth: Ignore BR/EDR packet size constraints when fragmenting for AMP Andrei Emeltchenko
2012-10-11 15:12 ` Marcel Holtmann
2012-10-11 14:48 ` [RFC 5/6] Bluetooth: Add L2CAP create channel request handling Andrei Emeltchenko
2012-10-11 15:13 ` Marcel Holtmann
2012-10-11 14:48 ` [RFC 6/6] Bluetooth: Fix error code byte order Andrei Emeltchenko
2012-10-11 15:11 ` Marcel Holtmann
2012-10-11 15:12 ` [RFC 1/6] Bluetooth: Add new l2cap_chan struct members for high speed channels Marcel Holtmann
2012-10-11 15:58 ` Mat Martineau
2012-10-11 17:39 ` Marcel Holtmann
2012-10-12 7:25 ` Andrei Emeltchenko [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121012072513.GB28051@aemeltch-MOBL1 \
--to=andrei.emeltchenko.news@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mathewm@codeaurora.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox