public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Pelly <npelly@google.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: l2ping only works for 10 seconds with 2.6.27
Date: Tue, 25 Nov 2008 23:52:57 -0800	[thread overview]
Message-ID: <35c90d960811252352u5c7446dctba559babc2a80f7@mail.gmail.com> (raw)
In-Reply-To: <EC7BE40B-98DD-40A8-BAD8-756C6D998AF2@holtmann.org>

On Tue, Nov 25, 2008 at 9:00 PM, Marcel Holtmann <marcel@holtmann.org> wrote:
> Hi Nick,
>
>> I have noticed with 2.6.27 that a bluez receiving side of l2ping will
>> detch the ACL connection (preventing further l2cap echos) after 10
>> seconds. HCI log below.
>>
>> Is this by design, or was it unintentional?
>
> it is not fully intentional, but it result due the fact on how we had to
> implement the Simple Pairing support. Problem here is that l2ping can not
> create a remote reference count of the connection. So BlueZ will clean up
> the ACL link. And we do have to do that since otherwise we waste power with
> an unused link.

Yeah I think it is an ok policy, like you say its bad for power to
maintain to link with no local client using it.

> So if you do l2test -P 1 -n <bdaddr> first and then l2ping you will see that
> the ACL link stays up since the l2test hold a remote reference count.

Ok, that'll do for a workaround for testing.

By the way, what happened to the HCI_UART_DEBUG patch I sent a few days ago?

Thanks,

Nick

      reply	other threads:[~2008-11-26  7:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-26  1:38 l2ping only works for 10 seconds with 2.6.27 Nick Pelly
2008-11-26  5:00 ` Marcel Holtmann
2008-11-26  7:52   ` Nick Pelly [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=35c90d960811252352u5c7446dctba559babc2a80f7@mail.gmail.com \
    --to=npelly@google.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