All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Singer <steven.singer@csr.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Florian Echtler <echtler@fs.tum.de>,
	Olivier Bornet <olivier.bornet@smartdata.ch>,
	BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] bthid cvs question
Date: Mon, 05 Jan 2004 21:21:10 +0000	[thread overview]
Message-ID: <3FF9D546.9040005@csr.com> (raw)
In-Reply-To: <1073329354.2508.26.camel@pegasus>

Marcel Holtmann wrote:
>>A lot of devices use page scan repetition mode R2 by default as it's the
>>lowest power mode.
> 
> the most device I have seen are using R1 by default and the only R2 are
> my HID devices.

Headsets can use R2. Basically any battery powered device that needs to
be connectable for long periods of time will be a candidate for using R2.

> I am no baseband expert, so let me see if I understand you right. In the
> case we don't know the page scan repetition mode we should use R2 in
> prefer of R1 or even R0? 

Correct.

 >                          Does this have disadvantages if the devices is
> in R1 or R0 mode? I ask because we found that connecting with R1 by
> default gives us a significant page time improvement.

The disadvantage of always using R2 is that you connect more slowly to
unknown devices than you might do if you used R1.

The advantage of using R2 is that you can connect to all devices. If you
use R1 then there may be many devices out there that you cannot connect
to (or that you connect to unreliably).

The worst case baseband connection times for different scenarios are:

slave sr \ master psrm  R0        R1        R2
R0                      0.20s     1.28s     2.56s
R1                      infinity  2.56s     3.84s
R2                      infinity  infinity  5.12s

> If only R2 makes sense in case that we don't the exact value, somebody
> should bring up an errata to the HCI working group ;)

The note from the baseband needs to be moved up to the HCI spec.

	- Steven
-- 



**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************

      reply	other threads:[~2004-01-05 21:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-09 17:28 [Bluez-users] bthid cvs question Jeffrey Arbuckle
2003-12-10  1:43 ` Marcel Holtmann
2003-12-10  8:02   ` Olivier Bornet
2003-12-10 14:18     ` Marcel Holtmann
2003-12-20 23:01       ` Florian Echtler
2003-12-21  1:25         ` [Bluez-devel] " Marcel Holtmann
2003-12-21 10:52           ` Florian Echtler
2003-12-21 11:56             ` [Bluez-devel] " Marcel Holtmann
2003-12-21 12:48               ` Florian Echtler
2003-12-21 13:14                 ` [Bluez-devel] " Marcel Holtmann
2004-01-05 16:44           ` Steven Singer
2004-01-05 19:02             ` [Bluez-devel] " Marcel Holtmann
2004-01-05 21:21               ` Steven Singer [this message]

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=3FF9D546.9040005@csr.com \
    --to=steven.singer@csr.com \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=echtler@fs.tum.de \
    --cc=marcel@holtmann.org \
    --cc=olivier.bornet@smartdata.ch \
    /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.