From: Marcel Holtmann <marcel@holtmann.org>
To: Ville Tervo <ville.tervo@nokia.com>
Cc: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: sniff mode
Date: Wed, 26 Aug 2009 11:04:51 -0700 [thread overview]
Message-ID: <1251309891.2950.97.camel@localhost.localdomain> (raw)
In-Reply-To: <4A94E282.6010302@nokia.com>
Hi Ville,
> >>>> It is just me or hci_conn_enter_active_mode will never do what its
> >>>> name suggests. This check will always succeed:
> >>>>
> >>>> if (conn->mode != HCI_CM_SNIFF || !conn->power_save)
> >>>> goto timer;
> >>> so conn->power_save is used to disable automatic sniff mode for incoming
> >>> connections. Mainly HID since they manager it by themselves.
> >> Hmm, but this seems to be done for any device regardless of its type.
> >> So for example we start sending/receiving data to a headset it will
> >> triggers hci_conn_enter_active_mode which I thought would exit sniff
> >> mode, right? (yep, I have seem some headset that doesn't leave sniff
> >> mode by their own).
> >
> > I said this before. We need a socket option for L2CAP and RFCOMM that
> > can trigger leaving sniff mode even if the remote device initiated the
> > connection.
> >
>
> I guess I need to take this on my TODO list. Or is some one already
> working on this?
go ahead. I am not working on it and I don't know of anybody else who
has plans for it.
Regards
Marcel
prev parent reply other threads:[~2009-08-26 18:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 18:26 sniff mode Luiz Augusto von Dentz
2009-08-24 18:40 ` Marcel Holtmann
2009-08-24 19:26 ` Luiz Augusto von Dentz
2009-08-24 19:33 ` Marcel Holtmann
2009-08-24 20:58 ` Luiz Augusto von Dentz
2009-08-24 21:12 ` Marcel Holtmann
2009-08-26 7:21 ` Ville Tervo
2009-08-26 18:04 ` Marcel Holtmann [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=1251309891.2950.97.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=ville.tervo@nokia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox