linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gustavo Padovan <gustavo@padovan.org>
To: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [RFC 4/5] Bluetooth: Process receiving FCS_NONE in L2CAP Conf Rsp
Date: Thu, 29 Nov 2012 08:27:47 -0200	[thread overview]
Message-ID: <20121129102747.GB26707@joana> (raw)
In-Reply-To: <1354118382-25571-4-git-send-email-Andrei.Emeltchenko.news@gmail.com>

Hi Andrei,

* Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com> [2012-11-28 17:59:41 +0200]:

> From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
> 
> Process L2CAP Config rsp Pending with FCS Option 0x00 (No FCS)
> which is sent by Motorola Windows 7 Bluetooth stack. The trace
> is shown below (all other options are skipped).
> 
> ...
> < ACL data: handle 1 flags 0x00 dlen 48
>     L2CAP(s): Config req: dcid 0x0043 flags 0x00 clen 36
>       ...
>       FCS Option 0x00 (No FCS)
> > ACL data: handle 1 flags 0x02 dlen 48
>     L2CAP(s): Config req: dcid 0x0041 flags 0x00 clen 36
>       ...
>       FCS Option 0x01 (CRC16 Check)
> < ACL data: handle 1 flags 0x00 dlen 47
>     L2CAP(s): Config rsp: scid 0x0043 flags 0x00 result 4 clen 33
>       Pending
>       ...
> > ACL data: handle 1 flags 0x02 dlen 50
>     L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 4 clen 36
>       Pending
>       ...
>       FCS Option 0x00 (No FCS)
> < ACL data: handle 1 flags 0x00 dlen 14
>     L2CAP(s): Config rsp: scid 0x0043 flags 0x00 result 0 clen 0
>       Success
> > ACL data: handle 1 flags 0x02 dlen 14
>     L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 0 clen 0
>       Success
> ...
> 
> Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
> ---
>  net/bluetooth/l2cap_core.c |    6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/net/bluetooth/l2cap_core.c b/net/bluetooth/l2cap_core.c
> index f10e4be..d30978b 100644
> --- a/net/bluetooth/l2cap_core.c
> +++ b/net/bluetooth/l2cap_core.c
> @@ -3429,6 +3429,12 @@ static int l2cap_parse_conf_rsp(struct l2cap_chan *chan, void *rsp, int len,
>  			l2cap_add_conf_opt(&ptr, L2CAP_CONF_EFS, sizeof(efs),
>  					   (unsigned long) &efs);
>  			break;
> +
> +		case L2CAP_CONF_FCS:
> +			if (*result == L2CAP_CONF_PENDING)
> +				if (val == L2CAP_FCS_NONE)
> +					set_bit(CONF_NO_FCS_RECV, &chan->conf_state);

Please break a line here as well.

	Gustavo

  reply	other threads:[~2012-11-29 10:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-28 15:59 [RFC 1/5] Bluetooth: AMP: Check that AMP is present and active Andrei Emeltchenko
2012-11-28 15:59 ` [RFC 2/5] Bluetooth: Refactor l2cap_send_disconn_req Andrei Emeltchenko
2012-11-28 15:59 ` [RFC 3/5] Bluetooth: Fix missing L2CAP EWS Conf parameter Andrei Emeltchenko
2012-11-29 10:25   ` Gustavo Padovan
2012-11-29 10:38     ` Andrei Emeltchenko
2012-11-28 15:59 ` [RFC 4/5] Bluetooth: Process receiving FCS_NONE in L2CAP Conf Rsp Andrei Emeltchenko
2012-11-29 10:27   ` Gustavo Padovan [this message]
2012-11-28 15:59 ` [RFC 5/5] Bluetooth: AMP: Mark controller radio powered down after HCIDEVDOWN Andrei Emeltchenko
2012-11-29 10:34   ` Gustavo Padovan
2012-11-29 15:46     ` [PATCHv2 1/4] Bluetooth: AMP: Check that AMP is present and active Andrei Emeltchenko
2012-11-29 15:46       ` [PATCHv2 2/4] Bluetooth: Fix missing L2CAP EWS Conf parameter Andrei Emeltchenko
2012-11-29 15:46       ` [PATCHv2 3/4] Bluetooth: Process receiving FCS_NONE in L2CAP Conf Rsp Andrei Emeltchenko
2012-11-29 15:46       ` [PATCHv2 4/4] Bluetooth: trivial: Change NO_FCS_RECV to RECV_NO_FCS Andrei Emeltchenko
2012-11-30 17:50         ` Gustavo Padovan

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=20121129102747.GB26707@joana \
    --to=gustavo@padovan.org \
    --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 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).