All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Norris <briannorris@chromium.org>
To: Francesco Dolcini <francesco@dolcini.it>
Cc: rafael@beims.me, Rafael Beims <rafael.beims@toradex.com>,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] wifi: mwifiex: enable host mlme on sdio W8997 chipsets
Date: Wed, 28 May 2025 10:05:03 -0700	[thread overview]
Message-ID: <aDdCP_lvlyvk9J3n@google.com> (raw)
In-Reply-To: <20250523072604.GA14001@francesco-nb>

Hi Francesco,

On Fri, May 23, 2025 at 09:26:04AM +0200, Francesco Dolcini wrote:
> On Thu, May 22, 2025 at 10:24:14AM -0700, Brian Norris wrote:
> > On Wed, May 21, 2025 at 07:19:34AM -0300, rafael@beims.me wrote:
> > > From: Rafael Beims <rafael.beims@toradex.com>
> > > 
> > > Enable the host mlme flag for W8997 chipsets so WPA3 can be used.
> > > This feature depends on firmware support (V2 API key), which may not be
> > > available in all available firmwares.
> > 
> > Is it available in *any* W8997 firmware? Or particularly, is it
> > available in the firmware in linux-firmware.git? Judging by its git
> > history, the answer is "no", in which case this is definitely NAK'd.
> 
> mrvl/sdsd8997_combo_v4.bin, from linux-firmware GIT, 16.92.21.p137
> version. From an off-list chat with Rafael he confirmed me that this is
> what he used for testing.

linux-firmware.git claims to hold W16.68.1.p197.1. Either WHENCE is
wrong, or that sounds like a completely different branch. Are you sure
about that?

> > users on the old FW version. So, we'd need to teach the driver to know
> > the difference between v1 and v2 API here, and choose accordingly.
> 
> This is already implemented. From mwifiex_ret_get_hw_spec()
> 
> ```
>         if (adapter->key_api_major_ver != KEY_API_VER_MAJOR_V2)
>                 adapter->host_mlme_enabled = false;
> ```


Huh, I forgot about that. I also assumed "v2 API" wasn't something
available on most older chips, but I guess I might have been wrong.

> To me the patch is ok.

The firmware versions above don't match up to me. But if we confirm
that:
(a) this API is available in a linux-firmware.git firmware for this chip
    and
(b) someone includes a valid linux-firmware.git version that they tested
    in the changelog

then maybe this is OK. As it stands now though, no.

Brian

  reply	other threads:[~2025-05-28 17:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-21 10:19 [PATCH] wifi: mwifiex: enable host mlme on sdio W8997 chipsets rafael
2025-05-22 17:24 ` Brian Norris
2025-05-23  7:26   ` Francesco Dolcini
2025-05-28 17:05     ` Brian Norris [this message]
2025-05-29  7:20       ` Francesco Dolcini
2025-05-28 10:48 ` Francesco Dolcini

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=aDdCP_lvlyvk9J3n@google.com \
    --to=briannorris@chromium.org \
    --cc=francesco@dolcini.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rafael.beims@toradex.com \
    --cc=rafael@beims.me \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.