From: Johannes Berg <johannes@sipsolutions.net>
To: "Sumangala, Suraj" <surajs@qca.qualcomm.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
"linville@tuxdriver.com" <linville@tuxdriver.com>,
"Balasubramanian, senthilkumar" <senthilb@qca.qualcomm.com>,
"Mehta, Vipin" <vipimeht@qca.qualcomm.com>,
"Valo, Kalle" <kvalo@qca.qualcomm.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: RE: [RFC] nl80211: Added NL80211 commands for Bluetooth-WiFi coex
Date: Fri, 02 Sep 2011 14:04:22 +0200 [thread overview]
Message-ID: <1314965062.3927.7.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <480687D4EEFE7447A2E09AADFF6673621AF82B5C@nasanexd02a.na.qualcomm.com>
On Fri, 2011-09-02 at 07:54 +0000, Sumangala, Suraj wrote:
> If we can provide "hci_dev" as the handle to the Bluetooth core, does
> it make sense to follow the below steps to send channel
> classification?
> 1. Implement an NL80211 command to provide the Bluetooth BDADDR.
> 2. Send it down to the WiFi driver via a cfg80211 API.
> 3. Let it call "hci_get_route" to get a hci_hdev handle.
> 4. Export an API to set channel classification in Bluetooth HCI core.
> 5. Let the WiFi driver form the channel classification and call the
> Bluetooth core "write channel classification" API to set the channels.
I don't see any reason to have a specific wifi device talk to a specific
BT device. The channel exclusion makes more sense if all wifi devices
and all BT devices are taken into account. As such, only simple API is
needed to let cfg80211 tell bluez about the channels, and then bluez can
multiplex it out to all its BT devices.
johannes
next prev parent reply other threads:[~2011-09-02 12:04 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
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 [this message]
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=1314965062.3927.7.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=marcel@holtmann.org \
--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