All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Padovan <gustavo@padovan.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: Set different event mask for LE-only controllers
Date: Thu, 15 Aug 2013 10:16:45 +0200	[thread overview]
Message-ID: <20130815081645.GC1980@joana> (raw)
In-Reply-To: <1376413254-36536-1-git-send-email-marcel@holtmann.org>

Hi Marcel,

* Marcel Holtmann <marcel@holtmann.org> [2013-08-13 10:00:54 -0700]:

> In case of a Low Energy only controller it makes no sense to configure
> the full BR/EDR event mask. It will just enable events that can not be
> send anyway and there is no guarantee that such a controller will accept
> this value.
> 
> Use event mask 0x90 0xe8 0x04 0x02 0x00 0x80 0x00 0x20 for LE-only
> controllers which enables the following events:
> 
>           Disconnection Complete
>           Encryption Change
>           Read Remote Version Information Complete
>           Command Complete
>           Command Status
>           Hardware Error
>           Number of Completed Packets
>           Data Buffer Overflow
>           Encryption Key Refresh Complete
>           LE Meta
> 
> This is according to Core Specification, Part E, Section 3.
> 
> Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
> ---
>  net/bluetooth/hci_core.c | 12 ++++++++++++
>  1 file changed, 12 insertions(+)

Patch has been applied to bluetooth-next. Thanks.

	Gustavo

  reply	other threads:[~2013-08-15  8:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-13 17:00 [PATCH] Bluetooth: Set different event mask for LE-only controllers Marcel Holtmann
2013-08-15  8:16 ` Gustavo Padovan [this message]
2013-08-15  8:18 ` 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=20130815081645.GC1980@joana \
    --to=gustavo@padovan.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.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.