From: Johannes Berg <johannes@sipsolutions.net>
To: Suraj Sumangala <surajs@qca.qualcomm.com>
Cc: linville@tuxdriver.com, ath6kl-devel@qualcomm.com,
senthilb@qca.qualcomm.com, vipimeht@qca.qualcomm.com,
kvalo@qca.qualcomm.com, linux-wireless@vger.kernel.org
Subject: Re: [RFC] nl80211: Added NL80211 commands for Bluetooth-WiFi coex
Date: Wed, 31 Aug 2011 08:30:17 +0200 [thread overview]
Message-ID: <1314772217.4161.10.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1314771915-8848-1-git-send-email-surajs@qca.qualcomm.com> (sfid-20110831_082525_612687_34CC3735)
On Wed, 2011-08-31 at 11:55 +0530, Suraj Sumangala wrote:
> This patch propose a new set of NL80211 commands and attributes
> to communicate information about ongoing Bluetooth operations to the
> wifi chip in case of a Bluetooth-WiFi coex solution.
>
> It can then be used by the WiFi hardware to understand the requirements
> of a Bluetooth radio and manage shared resources between
> Bluetooth and Wifi modules better.
>
> The proposed Bluetooth information sent are mainly regarding Bluetooth
> SCO, A2DP connection, inquiry and master/slave role of Bluetooth chip.
>
> This information can be sent by a userspace Bluetooth filter utility
> application to the WiFi driver.
???
Why would this need a userspace utility? Are you cloning some sort of
windows architecture here?
johannes
next prev parent reply other threads:[~2011-08-31 6:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 6:25 [RFC] nl80211: Added NL80211 commands for Bluetooth-WiFi coex Suraj Sumangala
2011-08-31 6:30 ` Johannes Berg [this message]
2011-08-31 6:36 ` Sumangala, Suraj
2011-08-31 6:40 ` Johannes Berg
2011-08-31 6:48 ` Sumangala, Suraj
2011-08-31 14:40 ` Marcel Holtmann
2011-08-31 14:56 ` Sumangala, Suraj
2011-08-31 22:51 ` Marcel Holtmann
2011-09-01 6:09 ` Sumangala, Suraj
2011-09-01 11:43 ` Marcel Holtmann
2011-09-01 12:20 ` Johannes Berg
2011-09-01 12:22 ` Kalle Valo
2011-09-02 7:54 ` Sumangala, Suraj
2011-09-02 12:04 ` Johannes Berg
2011-08-31 7:14 ` Johannes Berg
2011-08-31 14:30 ` Sumangala, Suraj
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=1314772217.4161.10.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath6kl-devel@qualcomm.com \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=senthilb@qca.qualcomm.com \
--cc=surajs@qca.qualcomm.com \
--cc=vipimeht@qca.qualcomm.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