From: Johannes Berg <johannes@sipsolutions.net>
To: Piotr Haber <phaber@broadcom.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/2] [RFC] cfg80211: configuration of Bluetooth coexistence mode
Date: Fri, 22 Feb 2013 12:52:04 +0100 [thread overview]
Message-ID: <1361533924.8146.5.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1361524092-4814-2-git-send-email-phaber@broadcom.com> (sfid-20130222_100804_524805_03F665CB)
On Fri, 2013-02-22 at 10:08 +0100, Piotr Haber wrote:
> Some devices share antenna/analog front end between Wifi
> and Bluetooth. The hardware coexistence interface allows
> them to do so, but there are situations when it would
> be beneficial if software had a way to have influence on it
> as well. It can be used to protect time sensitive
> traffic in presence of Bluetooth voice stream,
> for an example EAPOL handshake or DHCP negotiation.
>
> This patch adds new attribute to SET_WIPHY command
> and a new field in struct wiphy to allow control of the
> coexistence behavior. Devices that do not share resources
> with Bluetooth can ignore this parameter.
Apart from a few minor technical comments that I'll omit for now, I'm
not sure what value this really has? EAPOL can already be "protected" by
way of knowing when the station is marked authorized, and DHCP is pretty
tricky because it could take "forever", might not be there at all, etc.
What application would actually call this? I don't really see how it
could be integrated like that.
johannes
next prev parent reply other threads:[~2013-02-22 11:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 9:08 [RFC 0/2] control Bluetooth coexistence Piotr Haber
2013-02-22 9:08 ` [PATCH 1/2] [RFC] cfg80211: configuration of Bluetooth coexistence mode Piotr Haber
2013-02-22 11:52 ` Johannes Berg [this message]
2013-02-22 13:32 ` Piotr Haber
2013-02-22 14:07 ` Johannes Berg
2013-02-22 14:59 ` Piotr Haber
2013-02-22 9:08 ` [PATCH 2/2] brcmfmac: control BT coexistence parameters Piotr Haber
-- strict thread matches above, loose matches on Subject: below --
2013-02-22 16:59 [PATCH 1/2] [RFC] cfg80211: configuration of Bluetooth coexistence mode Arend Van Spriel
2013-02-22 20:28 ` Johannes Berg
2013-02-23 0:30 ` Adrian Chadd
2013-02-23 17:47 ` Arend Van Spriel
2013-02-24 9:12 ` Emmanuel Grumbach
2013-02-24 17:28 ` Johannes Berg
2013-02-25 5:08 ` Adrian Chadd
2013-02-25 5:54 ` Felix Fietkau
2013-02-25 10:11 ` Arend van Spriel
2013-02-25 10:25 ` Johannes Berg
2013-02-25 13:07 ` Felix Fietkau
2013-02-27 10:27 ` Dan Williams
2013-02-27 17:44 ` Arend van Spriel
2013-02-28 11:53 ` Piotr Haber
2013-02-27 18:45 ` Johannes Berg
2013-02-27 17:21 ` Arend van Spriel
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=1361533924.8146.5.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=phaber@broadcom.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).