linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: Tamizh chelvam <tamizhr@codeaurora.org>,
	johannes@sipsolutions.net, Marcel Holtmann <marcel@holtmann.org>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Linux Bluetooth mailing list <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH 1/2] cfg80211: Add support to enable or disable btcoex
Date: Fri, 2 Mar 2018 10:45:15 +0100	[thread overview]
Message-ID: <5A991D2B.60303@broadcom.com> (raw)
In-Reply-To: <87po4ndpos.fsf@purkki.adurom.net>

+ Marcel

On 3/2/2018 6:14 AM, Kalle Valo wrote:
> Arend van Spriel <arend.vanspriel@broadcom.com> writes:
>
>> On 3/1/2018 6:59 PM, Tamizh chelvam wrote:
>>> From: Tamizh chelvam <tamizhr@codeaurora.org>
>>>
>>> This patch introduces NL80211_CMD_SET_BTCOEX command and
>>> NL80211_ATTR_BTCOEX_OP attribute to enable or disable btcoex.
>>
>> What kind of btcoex are we talking about here? Is it signalling
>> between wlan and bt to get access to the shared RF.
>
> Yes, at least that's how I understand this.
>
>> Why would it require user-space interaction? Are there no options for
>> wlan to detect bt is in use, ie. bt hci is setup, and vice versa. Can
>> it be indicated in platform data or device tree. Trying to understand
>> the use-case here.
>
> One use case is being able to disable btcoex in case of problems or to
> test if it's btcoex related. I think during the last five years the need
> for this interface has come every once in a while.

Well, you would want to disable btcoex *and* bt to verify wlan is 
working properly on its own. And similarly disable btcoex *and* wlan to 
verify bt works properly.

Now I do recall a thread between you and Marcel. Looked it up and it was 
this thread [1], but did not see a follow-up on it. I suspect it 
involves more than just an enable/disable state. That may be fine for 
devices in which BT and WLAN are integrated and coordination of RF use 
is done on the device. The "btcoex subsystem" thread seems to aim for 
more like providing the coordination logic so independent BT device and 
WLAN device can still use the same RF. So before adopting the api in 
nl80211 it would be good to revive that thread.

Regards,
Arend

[1] https://www.spinics.net/lists/linux-wireless/msg133333.html

  reply	other threads:[~2018-03-02  9:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-01 17:59 [PATCH 1/2] cfg80211: Add support to enable or disable btcoex Tamizh chelvam
2018-03-01 17:59 ` [PATCH 2/2] mac80211: " Tamizh chelvam
2018-03-01 19:38 ` [PATCH 1/2] cfg80211: " Arend van Spriel
2018-03-02  5:14   ` Kalle Valo
2018-03-02  9:45     ` Arend van Spriel [this message]
2018-03-02  9:59       ` Marcel Holtmann
2018-03-02 10:38         ` Arend van Spriel
2018-03-13 14:45       ` 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=5A991D2B.60303@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --cc=johannes@sipsolutions.net \
    --cc=kvalo@codeaurora.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=tamizhr@codeaurora.org \
    /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).