public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Norris <briannorris@chromium.org>
To: Alex Bee <knaerzche@gmail.com>
Cc: Amitkumar Karwar <amitkumar.karwar@nxp.com>,
	Ganapathi Bhat <ganapathi.bhat@nxp.com>,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] wifi: mwifiex: Restore USB8897 chipset support
Date: Wed, 6 Dec 2023 11:13:41 -0800	[thread overview]
Message-ID: <ZXDH5S7rM32y48Fc@google.com> (raw)
In-Reply-To: <ZXDHgo5QnZjb237S@google.com>

(Altering CC list; sorry, I didn't notice the RESEND at first)

On Wed, Dec 06, 2023 at 11:12:02AM -0800, Brian Norris wrote:
> On Tue, Dec 05, 2023 at 10:02:37PM +0100, Alex Bee wrote:
> > This patch restores USB8897 support which was removed with
> > Commit 60a188a2715f ("mwifiex: remove USB8897 chipset support")
> 
> Did you look at the reason for that removal?
> 
> "if both mwifiex_pcie and mwifiex_usb modules are enabled by user,
> sometimes mwifiex_usb wins the race even if user wants wlan interface to
> be on PCIe and USB for bluetooth. This patch solves the problem."
> 
> That sounds like a legitimate problem, even if the solution isn't
> perfect. Do you have any alternatives?
> 
> I don't have such hardware, so I don't know its behaviors nor can I test
> it. But it'd be nice if we could differentiate USB-only vs PCIe+USB
> somehow.
> 
> > There are quite some devices which use this chipset with USB interface.
> > The firmware still exits in linux upstream firmware repo and this simple
> > patch is all what is required to support it in upstream linux (again).
> > 
> > Signed-off-by: Alex Bee <knaerzche@gmail.com>
> > ---
> > Recently I upstreamed support for Geniatec XPI-3128 SBC which actually
> > has one any of those boards soldered to the onboard USB Host controller.
> > Geniatech has some boards [0], [1], [2] (maybe more) which have this
> > variant soldered the same way. (optional)
> > I've also read that "Xbox Wireless adapter for Windows" uses this chipset
> > (unverified).
> > I've also CC'ed Ganapathi Bhat who last updated the firmware for SDIO and
> > PCIe variant of this chipset: It would be great if the firmware
> > for USB variant could get an update too, as the one which we currently
> > have is quite old - version 15.68.4.p103, while other have some 16.*
> > firmware. 
> 
> The old maintainers here seem to have gone AWOL, so I wouldn't hold my
> breath on getting any support from them.
> 
> Brian
> 
> > [0] https://www.geniatech.com/product/xpi-3288/
> > [1] https://www.geniatech.com/product/xpi-imx8mm/
> > [2] https://www.geniatech.com/product/xpi-s905x/
> >  
> >  drivers/net/wireless/marvell/mwifiex/Kconfig |  4 ++--
> >  drivers/net/wireless/marvell/mwifiex/usb.c   | 14 ++++++++++++++
> >  drivers/net/wireless/marvell/mwifiex/usb.h   |  3 +++
> >  3 files changed, 19 insertions(+), 2 deletions(-)
> 

  reply	other threads:[~2023-12-06 19:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05 21:02 [PATCH] wifi: mwifiex: Restore USB8897 chipset support Alex Bee
2023-12-06 19:12 ` Brian Norris
2023-12-06 19:13   ` Brian Norris [this message]
2023-12-06 21:51     ` Alex Bee
2023-12-14  1:31       ` Brian Norris

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=ZXDH5S7rM32y48Fc@google.com \
    --to=briannorris@chromium.org \
    --cc=amitkumar.karwar@nxp.com \
    --cc=ganapathi.bhat@nxp.com \
    --cc=knaerzche@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.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