From: Gustavo Padovan <padovan@profusion.mobi>
To: Emeltchenko Andrei <Andrei.Emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [RFC 5/7] Bluetooth: parse EFS in l2cap config response
Date: Wed, 24 Aug 2011 18:15:48 -0300 [thread overview]
Message-ID: <20110824211548.GI2662@joana> (raw)
In-Reply-To: <1313653502-6303-6-git-send-email-Andrei.Emeltchenko.news@gmail.com>
Hi Andrei,
* Emeltchenko Andrei <Andrei.Emeltchenko.news@gmail.com> [2011-08-18 10:45:00 +0300]:
> From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
>
> Add parsing extended flowspec in l2cap config response
> Based upon haijun.liu <haijun.liu@atheros.com> series of patches
> (sent Sun, 22 Aug 2010)
> ---
> net/bluetooth/l2cap_core.c | 28 +++++++++++++++++++++++++++-
> 1 files changed, 27 insertions(+), 1 deletions(-)
>
> diff --git a/net/bluetooth/l2cap_core.c b/net/bluetooth/l2cap_core.c
> index 5378bc6..f64c9cb 100644
> --- a/net/bluetooth/l2cap_core.c
> +++ b/net/bluetooth/l2cap_core.c
> @@ -2213,6 +2213,7 @@ static int l2cap_parse_conf_rsp(struct l2cap_chan *chan, void *rsp, int len, voi
> int type, olen;
> unsigned long val;
> struct l2cap_conf_rfc rfc;
> + struct l2cap_conf_efs efs;
>
> BT_DBG("chan %p, rsp %p, len %d, req %p", chan, rsp, len, data);
>
> @@ -2248,6 +2249,19 @@ static int l2cap_parse_conf_rsp(struct l2cap_chan *chan, void *rsp, int len, voi
> l2cap_add_conf_opt(&ptr, L2CAP_CONF_RFC,
> sizeof(rfc), (unsigned long) &rfc);
> break;
> +
> + case L2CAP_CONF_EFS:
> + if (olen == sizeof(efs))
> + memcpy(&efs, (void *)val, olen);
> +
> + if (chan->local_stype != L2CAP_SERVTYPE_NOTRAFIC &&
> + efs.service_type != L2CAP_SERVTYPE_NOTRAFIC &&
> + efs.service_type != chan->local_stype)
> + return -ECONNREFUSED;
> +
> + l2cap_add_conf_opt(&ptr, L2CAP_CONF_EFS,
> + sizeof(efs), (unsigned long) &efs);
> + break;
> }
> }
>
> @@ -2256,13 +2270,25 @@ static int l2cap_parse_conf_rsp(struct l2cap_chan *chan, void *rsp, int len, voi
>
> chan->mode = rfc.mode;
>
> - if (*result == L2CAP_CONF_SUCCESS) {
> + if (*result == L2CAP_CONF_SUCCESS || *result == L2CAP_CONF_PENDING) {
> switch (rfc.mode) {
> case L2CAP_MODE_ERTM:
> chan->retrans_timeout = le16_to_cpu(rfc.retrans_timeout);
> chan->monitor_timeout = le16_to_cpu(rfc.monitor_timeout);
> chan->mps = le16_to_cpu(rfc.max_pdu_size);
> + if (chan->ext_flowspec_enable) {
> + /* id, service type should not be changed */
> + chan->local_msdu =
> + le16_to_cpu(efs.max_sdu_size);
> + chan->local_sdu_itime =
> + le32_to_cpu(efs.sdu_inter_time);
> + chan->local_acc_lat =
> + le32_to_cpu(efs.access_latency);
> + chan->local_flush_to =
> + le32_to_cpu(efs.flush_timeout);
> + }
These should be the remote_ not the local_ values.
Gustavo
next prev parent reply other threads:[~2011-08-24 21:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-18 7:44 [RFC 0/7] EFS initial support Emeltchenko Andrei
2011-08-18 7:44 ` [RFC 1/7] Bluetooth: L2CAP extended feature mask update Emeltchenko Andrei
2011-08-18 7:44 ` [RFC 2/7] Bluetooth: EFS: definitions and headers for EFS Emeltchenko Andrei
2011-08-24 20:43 ` Gustavo Padovan
2011-08-30 7:52 ` Emeltchenko Andrei
2011-08-24 20:46 ` Gustavo Padovan
2011-08-18 7:44 ` [RFC 3/7] Bluetooth: EFS: add disable_flowspec kernel param Emeltchenko Andrei
2011-08-18 7:44 ` [RFC 4/7] Bluetooth: parse EFS in l2cap config request Emeltchenko Andrei
2011-08-24 21:13 ` Gustavo Padovan
2011-08-30 12:28 ` Emeltchenko Andrei
2011-08-18 7:45 ` [RFC 5/7] Bluetooth: parse EFS in l2cap config response Emeltchenko Andrei
2011-08-24 21:15 ` Gustavo Padovan [this message]
2011-08-30 12:47 ` Emeltchenko Andrei
2011-08-18 7:45 ` [RFC 6/7] Bluetooth: add EFS option in l2cap conf req Emeltchenko Andrei
2011-08-24 21:30 ` Gustavo Padovan
2011-08-30 13:54 ` Emeltchenko Andrei
2011-08-24 21:33 ` Gustavo Padovan
2011-08-30 13:57 ` Emeltchenko Andrei
2011-08-18 7:45 ` [RFC 7/7] Bluetooth: EFS: parse l2cap config rsp pending Emeltchenko Andrei
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=20110824211548.GI2662@joana \
--to=padovan@profusion.mobi \
--cc=Andrei.Emeltchenko.news@gmail.com \
--cc=linux-bluetooth@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.