From: Gustavo Padovan <padovan@profusion.mobi>
To: Anderson Lizardo <anderson.lizardo@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: use recommended LE connection parameters
Date: Mon, 1 Aug 2011 16:20:43 -0300 [thread overview]
Message-ID: <20110801192043.GB4430@joana> (raw)
In-Reply-To: <1311802809-10565-1-git-send-email-anderson.lizardo@openbossa.org>
* Anderson Lizardo <anderson.lizardo@openbossa.org> [2011-07-27 18:40:09 -0300]:
> The new connection parameters now match the recommended values for
> Proximity and Health Thermometer profiles. The previous values were
> ramdomly chosen, and are either too low or too high for most cases.
>
> New values:
>
> Scan Interval: 60 ms
> Scan Window: 30 ms
> Minimum Connection Interval: 50 ms
> Maximum Connection Interval: 70 ms
> Supervision Timeout: 420 ms
>
> See "Table 5.2: Recommended Scan Interval and Scan Window Values" and
> "Table 5.3: Recommended Connection Interval Values" for both profiles
> for details. Note that the "fast connection" parameters were chosen,
> because we do not support yet dynamically changing these parameters from
> initiator side.
>
> Additionally, the Proximity profile recommends (section "4.4 Alert on
> Link Loss"):
>
> "It is recommended that the Link Supervision Timeout (LSTO) is set to 6x
> the connection interval."
>
> Minimum_CE_Length and Maximum_CE_Length were also changed from 0x0001 to
> 0x0000 because they are informational and optional, and old value was
> not reflecting reality.
> ---
> net/bluetooth/hci_conn.c | 14 +++++++-------
> 1 files changed, 7 insertions(+), 7 deletions(-)
Applied, and also added the Signed-off-by line that you forgot. Thanks.
Gustavo
next prev parent reply other threads:[~2011-08-01 19:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 21:40 [PATCH] Bluetooth: use recommended LE connection parameters Anderson Lizardo
2011-08-01 19:20 ` Gustavo Padovan [this message]
2011-08-01 19:36 ` Anderson Lizardo
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=20110801192043.GB4430@joana \
--to=padovan@profusion.mobi \
--cc=anderson.lizardo@openbossa.org \
--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