From: Antti Julku <antti.julku@nokia.com>
To: ext Claudio Takahasi <claudio.takahasi@openbossa.org>
Cc: Dmitriy Paliy <dmitriy.paliy@gmail.com>,
Marcel Holtmann <marcel@holtmann.org>,
linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: Add mgmt command for fast connectable mode
Date: Thu, 04 Aug 2011 11:44:43 +0300 [thread overview]
Message-ID: <4E3A5BFB.1050201@nokia.com> (raw)
In-Reply-To: <CAKT1EBfQaTSjQe6sZnC5Wx52iPmyo6SSfYD0Ci+_qb1Dbq32+g@mail.gmail.com>
Hi Claudio and Marcel,
On 07/25/2011 03:46 PM, ext Claudio Takahasi wrote:
> BTW, I think we need to align BR and LE. Proximity and Thermometer
> Profiles also have recommended parameters for fast connection(first
> 30sec) and 2 reduced power options. Both profiles use the same
> configuration. If we add a new command to control page/connection
> parameters it needs to be aligned with BR and LE and if possible
> avoiding transport specific parameters.
>
> BR,
> Claudio
This issue was discussed in the IRC. It seem that for LE, fast
connection is needed only on the initiator side for outgoing connections
(LE scan/connection establishment parameters), since 4.0 spec forbids LE
connections between dual mode devices. So fast connectable mode on the
LE acceptor side would be only used for testing purposes, or if spec is
changed, or if single mode hw is supported in the future.
For BR/EDR, as Dmitriy explained, the fast connectable use case is to
make headset to be able to connect faster when there is an incoming call
(user switches headset on when call is alerting). It's an enhancement
for headset connection time and usability.
It is currently implemented in hciops by changing page scan settings
while incoming call is alerting. HCI commands Write Page Scan Activity
and Write Page Scan Type are used to change page scan type from standard
to interlaced and interval 1.28 s => 22.5 ms. This makes the incoming
connection about 1 s faster. Settings are changed only for a short time
to minimize impact on power consumption.
In my opinion BR and LE cases are quite different, so I think it would
make sense to keep these separate and not to put them in one mgmt
command. Could we just add a generic mgmt command for setting BR page
scan parameters, for example "Set Page Scan Parameters Command" which
would take parameters type (standard or interlaced), interval, and window?
Br,
Antti
next prev parent reply other threads:[~2011-08-04 8:44 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
2011-07-25 11:34 ` Dmitriy Paliy
2011-07-25 12:46 ` Claudio Takahasi
2011-08-04 8:44 ` Antti Julku [this message]
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=4E3A5BFB.1050201@nokia.com \
--to=antti.julku@nokia.com \
--cc=claudio.takahasi@openbossa.org \
--cc=dmitriy.paliy@gmail.com \
--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 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).