linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, mathewm@codeaurora.org
Subject: Re: [RFC 1/6] Bluetooth: Add new l2cap_chan struct members for high speed channels
Date: Thu, 11 Oct 2012 17:12:14 +0200	[thread overview]
Message-ID: <1349968334.27233.182.camel@aeonflux> (raw)
In-Reply-To: <1349966905-32336-1-git-send-email-Andrei.Emeltchenko.news@gmail.com>

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@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(+)

Acked-by: Marcel Holtmann <marcel@holtmann.org>

Regards

Marcel



  parent reply	other threads:[~2012-10-11 15:12 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 ` Marcel Holtmann [this message]
2012-10-11 15:58 ` [RFC 1/6] Bluetooth: Add new l2cap_chan struct members for high speed channels Mat Martineau
2012-10-11 17:39   ` Marcel Holtmann
2012-10-12  7:25   ` Andrei Emeltchenko

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=1349968334.27233.182.camel@aeonflux \
    --to=marcel@holtmann.org \
    --cc=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;
as well as URLs for NNTP newsgroup(s).