From: Brian Norris <briannorris@chromium.org>
To: David Lin <yu-hao.lin@nxp.com>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
kvalo@kernel.org, francesco@dolcini.it,
tsung-hsien.hsieh@nxp.com,
Francesco Dolcini <francesco.dolcini@toradex.com>
Subject: Re: [PATCH v11 2/2] wifi: mwifiex: add host mlme for AP mode
Date: Mon, 8 Jul 2024 12:26:40 -0700 [thread overview]
Message-ID: <Zow9cOyMvgiddkKw@google.com> (raw)
In-Reply-To: <20240704033001.603419-3-yu-hao.lin@nxp.com>
Hi David,
On Thu, Jul 04, 2024 at 11:30:01AM +0800, David Lin wrote:
> Add host based MLME to enable WPA3 functionalities in AP mode.
> This feature required a firmware with the corresponding V2 Key API
> support. The feature (WPA3) is currently enabled and verified only
> on IW416. Also, verified no regression with change when host MLME
> is disabled.
>
> Signed-off-by: David Lin <yu-hao.lin@nxp.com>
> Reviewed-by: Francesco Dolcini <francesco.dolcini@toradex.com>
> Acked-by: Brian Norris <briannorris@chromium.org>
> ---
>
> v11:
> - modify 'mwifiex_mgmt_stypes' to allow multi-adapters with different
> setting of host_mlme_enbaled.
...
> - wiphy->mgmt_stypes = mwifiex_mgmt_stypes;
> + if (adapter->host_mlme_enabled) {
> + memcpy(adapter->mwifiex_mgmt_stypes,
> + mwifiex_mgmt_stypes,
> + NUM_NL80211_IFTYPES *
> + sizeof(struct ieee80211_txrx_stypes));
> +
> + adapter->mwifiex_mgmt_stypes[NL80211_IFTYPE_AP].tx = 0xffff;
> + adapter->mwifiex_mgmt_stypes[NL80211_IFTYPE_AP].rx =
> + BIT(IEEE80211_STYPE_ASSOC_REQ >> 4) |
> + BIT(IEEE80211_STYPE_REASSOC_REQ >> 4) |
> + BIT(IEEE80211_STYPE_PROBE_REQ >> 4) |
> + BIT(IEEE80211_STYPE_DISASSOC >> 4) |
> + BIT(IEEE80211_STYPE_AUTH >> 4) |
> + BIT(IEEE80211_STYPE_DEAUTH >> 4) |
> + BIT(IEEE80211_STYPE_ACTION >> 4);
> + wiphy->mgmt_stypes = adapter->mwifiex_mgmt_stypes;
> + } else {
> + wiphy->mgmt_stypes = mwifiex_mgmt_stypes;
> + }
> wiphy->max_remain_on_channel_duration = 5000;
> wiphy->interface_modes = BIT(NL80211_IFTYPE_STATION) |
> BIT(NL80211_IFTYPE_P2P_CLIENT) |
...
> --- a/drivers/net/wireless/marvell/mwifiex/main.h
> +++ b/drivers/net/wireless/marvell/mwifiex/main.h
> @@ -1008,6 +1008,7 @@ struct mwifiex_adapter {
>
> bool ext_scan;
> bool host_mlme_enabled;
> + struct ieee80211_txrx_stypes mwifiex_mgmt_stypes[NUM_NL80211_IFTYPES];
This wasn't exactly what I had in mind by a "second copy" of
mwifiex_mgmt_stypes -- that you add a new array to mwifiex_adapter that
is only sometimes used. I meant something more like a const
'mwifiex_mgmt_stypes_mlme`, with the appropriate constant values. But I
suppose this works too, if a bit awkward, and saves a bit of code/data
duplication.
So, the 'Acked-by' still seems appropriate.
Thanks for the patience on this series.
Brian
next prev parent reply other threads:[~2024-07-08 19:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 3:29 [PATCH v11 0/2] wifi: mwifiex: add code to support host mlme David Lin
2024-07-04 3:30 ` [PATCH v11 1/2] wifi: mwifiex: add host mlme for client mode David Lin
2024-08-04 8:56 ` Kalle Valo
2024-07-04 3:30 ` [PATCH v11 2/2] wifi: mwifiex: add host mlme for AP mode David Lin
2024-07-08 19:26 ` Brian Norris [this message]
2024-07-09 2:26 ` [EXT] " David Lin
2024-07-10 1:47 ` [PATCH v11 0/2] wifi: mwifiex: add code to support host mlme David Lin
2024-07-10 8:02 ` Kalle Valo
2024-07-11 1:33 ` [EXT] " David Lin
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=Zow9cOyMvgiddkKw@google.com \
--to=briannorris@chromium.org \
--cc=francesco.dolcini@toradex.com \
--cc=francesco@dolcini.it \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=tsung-hsien.hsieh@nxp.com \
--cc=yu-hao.lin@nxp.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).