From: Marcel Holtmann <marcel@holtmann.org>
To: Antti Julku <antti.julku@nokia.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: Add mgmt command for fast connectable mode
Date: Tue, 28 Jun 2011 17:58:09 -0700 [thread overview]
Message-ID: <1309309092.2208.25.camel@aeonflux> (raw)
In-Reply-To: <1308737516-3303-1-git-send-email-antti.julku@nokia.com>
Hi Antti,
> Add command to management interface for enabling/disabling the
> fast connectable mode.
>
> Signed-off-by: Antti Julku <antti.julku@nokia.com>
> ---
> include/net/bluetooth/hci.h | 10 +++++++
> include/net/bluetooth/mgmt.h | 5 +++
> net/bluetooth/mgmt.c | 60 ++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 75 insertions(+), 0 deletions(-)
>
> diff --git a/include/net/bluetooth/hci.h b/include/net/bluetooth/hci.h
> index 65345cd..d7b9600 100644
> --- a/include/net/bluetooth/hci.h
> +++ b/include/net/bluetooth/hci.h
> @@ -698,6 +698,16 @@ struct hci_rp_read_bd_addr {
> bdaddr_t bdaddr;
> } __packed;
>
> +#define HCI_OP_WRITE_PAGE_SCAN_ACTIVITY 0x0c1c
> +struct hci_cp_write_page_scan_activity {
> + __le16 interval;
> + __le16 window;
> +} __packed;
> +
> +#define HCI_OP_WRITE_PAGE_SCAN_TYPE 0x0c47
> + #define PAGE_SCAN_TYPE_STANDARD 0x00
> + #define PAGE_SCAN_TYPE_INTERLACED 0x01
> +
> #define HCI_OP_LE_SET_EVENT_MASK 0x2001
> struct hci_cp_le_set_event_mask {
> __u8 mask[8];
> diff --git a/include/net/bluetooth/mgmt.h b/include/net/bluetooth/mgmt.h
> index 45bea25..7196d04 100644
> --- a/include/net/bluetooth/mgmt.h
> +++ b/include/net/bluetooth/mgmt.h
> @@ -209,6 +209,11 @@ struct mgmt_cp_unblock_device {
> bdaddr_t bdaddr;
> } __packed;
>
> +#define MGMT_OP_SET_FAST_CONNECTABLE 0x001F
> +struct mgmt_cp_set_fast_connectable {
> + __u8 enable;
> +} __packed;
> +
so I am not 100% sure that doing it this way is the best way.
What is the down side of just enabling interlaced page scan all the
time? And then maybe allow tuning of the timeout via debugfs for testing
purposes.
If we really wanna differentiate between connectable and fast
connectable, then we need to fix up also the controller information to
export this kind of detail. That will get pretty messy right now. So I
would really just prefer to go with interlaced page scan by default and
see what downside this gives us.
Regards
Marcel
next prev parent reply other threads:[~2011-06-29 0:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 10:11 [PATCH] Bluetooth: Add mgmt command for fast connectable mode Antti Julku
2011-06-29 0:58 ` Marcel Holtmann [this message]
2011-07-25 11:34 ` Dmitriy Paliy
2011-07-25 12:46 ` Claudio Takahasi
2011-08-04 8:44 ` Antti Julku
2011-08-10 9:33 ` Antti Julku
2011-08-10 13:55 ` Marcel Holtmann
2011-08-19 12:38 ` Antti Julku
2011-08-22 18:01 ` Gustavo Padovan
2011-08-22 18:40 ` Claudio Takahasi
2011-08-22 19:48 ` Gustavo Padovan
2011-08-23 6:03 ` Antti Julku
2011-07-25 13:38 ` Marcel Holtmann
2011-07-25 14:48 ` Dmitriy Paliy
-- strict thread matches above, loose matches on Subject: below --
2011-06-22 9:18 Antti Julku
2011-06-17 9:43 Antti Julku
2011-06-21 18:01 ` Gustavo F. Padovan
2011-06-16 11:54 Antti Julku
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=1309309092.2208.25.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=antti.julku@nokia.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).