All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Hurley <peter@hurleysoftware.com>
To: Anderson Lizardo <anderson.lizardo@openbossa.org>
Cc: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
	linux-bluetooth <linux-bluetooth@vger.kernel.org>
Subject: Re: [RFC v2 1/5] Bluetooth: Only schedule LE tx links if LE-capable
Date: Fri, 19 Aug 2011 09:36:29 -0400	[thread overview]
Message-ID: <1313760989.2585.54.camel@THOR> (raw)
In-Reply-To: <CAJdJm_OxbhXeLckhSFAnatYEE0ikKNVKxb=2wjEQ5vnMWjPYdQ@mail.gmail.com>

Hi Anderson,

On Fri, 2011-08-19 at 06:52 -0400, Anderson Lizardo wrote:
> Hi Peter,
> 
> On Thu, Aug 18, 2011 at 7:17 AM, Peter Hurley <peter@hurleysoftware.com> wrote:
> > On Thu, 2011-08-18 at 03:43 -0400, Luiz Augusto von Dentz wrote:
> >> Any reasons why you choose to not add the check inside hci_sched_le?
> >
> > Only to make it really obvious that LE transmission is not required on
> > the vast majority of BT controllers :)
> 
> ... yet. Are you aware LE is not optional on Bluetooth 4.0? Therefore
> any modern BT device claiming to support 4.0 will have LE support on
> its controller (host support is another thing).

I was aware of that, but that's an important point you make.

> But I suppose we will still see plenty of 2.1 devices for a long time...

As I noted to Andre earlier, this particular test will be unnecessary
when Luiz's proposal (using the LE connection count to bypass LE
scheduling when 0). I feel Luiz's approach is the more effective
approach anyway.

Regards,
Peter Hurley

  reply	other threads:[~2011-08-19 13:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-18  0:37 [RFC v2 1/5] Bluetooth: Only schedule LE tx links if LE-capable Peter Hurley
2011-08-18  7:43 ` Luiz Augusto von Dentz
     [not found]   ` <1313666245.17513.9.camel@THOR>
2011-08-19 10:52     ` Anderson Lizardo
2011-08-19 13:36       ` Peter Hurley [this message]
2011-08-18 22:12 ` Andre Guedes
2011-08-19 12:51   ` Peter Hurley

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=1313760989.2585.54.camel@THOR \
    --to=peter@hurleysoftware.com \
    --cc=anderson.lizardo@openbossa.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    /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.