linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: "Jonas Dreßler" <verdre@v0yd.nl>
Cc: "Amitkumar Karwar" <amitkarwar@gmail.com>,
	"Ganapathi Bhat" <ganapathi017@gmail.com>,
	"Xinming Hu" <huxinming820@gmail.com>,
	"Kalle Valo" <kvalo@codeaurora.org>,
	"David S. Miller" <davem@davemloft.net>,
	"Jakub Kicinski" <kuba@kernel.org>,
	"Tsuchiya Yuto" <kitakar@gmail.com>,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	"Maximilian Luz" <luzmaximilian@gmail.com>,
	"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Pali Rohár" <pali@kernel.org>
Subject: Re: [PATCH] mwifiex: Ignore BTCOEX events from the 88W8897 firmware
Date: Mon, 29 Nov 2021 17:38:24 -0600	[thread overview]
Message-ID: <20211129233824.GA2703817@bhelgaas> (raw)
In-Reply-To: <20211129233209.GA2702252@bhelgaas>

On Mon, Nov 29, 2021 at 05:32:11PM -0600, Bjorn Helgaas wrote:
> On Wed, Nov 03, 2021 at 09:58:27PM +0100, Jonas Dreßler wrote:
> > The firmware of the 88W8897 PCIe+USB card sends those events very
> > unreliably, sometimes bluetooth together with 2.4ghz-wifi is used and no
> > COEX event comes in, and sometimes bluetooth is disabled but the
> > coexistance mode doesn't get disabled.
> 
> s/sends those events/sends BTCOEX events/ so it reads well without the
> subject.
> 
> s/coexistance/coexistence/
> 
> Is BTCOEX a standard Bluetooth thing?  Is there a spec reference that
> could be useful here?  I've never seen those specs, so this is just
> curiosity.  I did download the "Bluetooth Core Spec v5.3", which does
> have a "Wireless Coexistence Signaling and Interfaces" chapter, but
> "BTCOEX" doesn't appear in that doc.
> 
> > This means we sometimes end up capping the rx/tx window size while
> > bluetooth is not enabled anymore, artifically limiting wifi speeds even
> > though bluetooth is not being used.
> 
> s/artifically/artificially/
> 
> > Since we can't fix the firmware, let's just ignore those events on the
> > 88W8897 device. From some Wireshark capture sessions it seems that the
> > Windows driver also doesn't change the rx/tx window sizes when bluetooth
> > gets enabled or disabled, so this is fairly consistent with the Windows
> > driver.

I hadn't read far enough to see that the patch was already applied,
sorry for the noise :)

  reply	other threads:[~2021-11-29 23:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-03 20:58 [PATCH] mwifiex: Ignore BTCOEX events from the 88W8897 firmware Jonas Dreßler
2021-11-26 16:30 ` Kalle Valo
2021-11-29 23:32 ` Bjorn Helgaas
2021-11-29 23:38   ` Bjorn Helgaas [this message]
2021-11-30 10:15     ` Jonas Dreßler

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=20211129233824.GA2703817@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=amitkarwar@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bhelgaas@google.com \
    --cc=davem@davemloft.net \
    --cc=ganapathi017@gmail.com \
    --cc=huxinming820@gmail.com \
    --cc=kitakar@gmail.com \
    --cc=kuba@kernel.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luzmaximilian@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pali@kernel.org \
    --cc=verdre@v0yd.nl \
    /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).