From: Pavel Machek <pavel@ucw.cz>
To: Arend van Spriel <arend@broadcom.com>
Cc: "Pali Rohár" <pali.rohar@gmail.com>,
"Kalle Valo" <kvalo@codeaurora.org>,
"Ivaylo Dimitrov" <ivo.g.dimitrov.75@gmail.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
"David Gnedt" <david.gnedt@davizone.at>
Subject: Re: [PATCH v2] wl1251: add sysfs interface for bluetooth coexistence mode configuration
Date: Thu, 14 Jan 2016 10:16:54 +0100 [thread overview]
Message-ID: <20160114091654.GA15380@amd> (raw)
In-Reply-To: <5696D08F.9030906@broadcom.com>
On Wed 2016-01-13 23:32:47, Arend van Spriel wrote:
> On 12/26/2015 12:45 PM, Pali Rohár wrote:
> >Port the bt_coex_mode sysfs interface from wl1251 driver version included
> >in the Maemo Fremantle kernel to allow bt-coexistence mode configuration.
> >This enables userspace applications to set one of the modes
> >WL1251_BT_COEX_OFF, WL1251_BT_COEX_ENABLE and WL1251_BT_COEX_MONOAUDIO.
> >The default mode is WL1251_BT_COEX_OFF.
> >It should be noted that this driver always enabled bt-coexistence before
> >and enabled bt-coexistence directly affects the receiving performance,
> >rendering it unusable in some low-signal situations. Especially monitor
> >mode is affected very badly with bt-coexistence enabled.
>
> So what user-space process will be using this interface. Did you consider
> adding debugfs interface? In case of monitor mode you could consider
> disabling bt-coex from within the driver itself.
This aint no debugging feature.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2016-01-14 9:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-26 11:45 [PATCH v2] wl1251: add sysfs interface for bluetooth coexistence mode configuration Pali Rohár
2016-01-09 20:33 ` Pali Rohár
2016-01-13 12:16 ` Pali Rohár
2016-01-13 12:57 ` Kalle Valo
2016-01-13 14:40 ` Pali Rohár
2016-01-13 22:32 ` Arend van Spriel
2016-01-13 22:39 ` Pali Rohár
2016-01-14 9:16 ` Pavel Machek [this message]
2016-01-21 8:53 ` Pali Rohár
2016-01-21 13:48 ` Kalle Valo
2016-01-21 13:51 ` Pali Rohár
2016-01-21 14:44 ` Kalle Valo
2016-01-22 9:29 ` Pali Rohár
2016-01-22 11:55 ` Kalle Valo
[not found] ` <1451130310-16666-1-git-send-email-pali.rohar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-01-21 13:44 ` Kalle Valo
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=20160114091654.GA15380@amd \
--to=pavel@ucw.cz \
--cc=arend@broadcom.com \
--cc=david.gnedt@davizone.at \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pali.rohar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).