linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Norris <briannorris@chromium.org>
To: David Lin <yu-hao.lin@nxp.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Kalle Valo <kvalo@kernel.org>,
	"francesco@dolcini.it" <francesco@dolcini.it>,
	Pete Hsieh <tsung-hsien.hsieh@nxp.com>,
	"rafael.beims" <rafael.beims@toradex.com>,
	Francesco Dolcini <francesco.dolcini@toradex.com>
Subject: Re: [EXT] [PATCH v10 0/2] wifi: mwifiex: add code to support host mlme
Date: Wed, 22 May 2024 17:50:26 -0700	[thread overview]
Message-ID: <Zk6S0m2U_xEojICb@google.com> (raw)
In-Reply-To: <PA4PR04MB96381B9675BCA5861AEDEF25D1E22@PA4PR04MB9638.eurprd04.prod.outlook.com>

On Mon, May 13, 2024 at 01:27:13AM +0000, David Lin wrote:
> > From: David Lin <yu-hao.lin@nxp.com>
> > Sent: Thursday, May 2, 2024 4:35 PM
> > 
> > 1. The process of external_auth should be as follows:
> >   a. cfg80211_ops.connect() is called to establish connection with remote
> > AP.
> >   b. If authentication is not WLAN_AUTH_SAE, FW will process
> > authentication/association
> >   and reply connection result to cfg80211.
> >   c. If authentication is WLAN_AUTH_SAE, FW should notify driver to call
> >   cfg80211_external_auth_request() to offload authentication to
> > wpa_supplicant.

FWIW, I expect you could just as well teach the driver to detect this --
I don't think we'd strictly require that firmware notify the driver.
Essentially, you could teach the driver to notice any sort of CONNECT
request (e.g., keep a list of FW-supported WLAN_AUTH_* modes?) that the
firmware can't handle on its own, and begin the external_auth() process.

I'm not sure this is ideal, but it does sound doable even without FW
notification.

> >   d. FW will wait for authentication result passed by
> > cfg80211_ops.external_auth() to
> >   decide if association should be processed with remote AP for the original
> > connection
> >   request and reply connection result to cfg80211.
> >   NXP FW only supports association with or without authentication, it can't
> > support external_auth.

But could it support my above description? Basically, the driver decides
whether to submit the connection request directly to the firmware, or
go with external_auth() instead.

> > 2. Hook separating auth/assoc will offload SME to wpa_supplicant
> > completely. Driver/FW don't need
> >   to involve the process of authentication just like external_auth did. There
> > is no effort for driver/FW
> >   to support any future modifications of authentication process.
> 
> Can we confirm that hooking separating auth/assoc is more suitable than "external_auth" for mwifiex?

I have one clarification question above. And I haven't heard anything
more from Marcel, so assuming the above is clarified, I suppose we can
drop the external_auth question.

Brian

  reply	other threads:[~2024-05-23  0:50 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-18  6:06 [PATCH v10 0/2] wifi: mwifiex: add code to support host mlme David Lin
2024-04-18  6:06 ` [PATCH v10 1/2] wifi: mwifiex: add host mlme for client mode David Lin
2024-04-18  6:37   ` Francesco Dolcini
2024-04-18  8:24     ` [EXT] " David Lin
2024-05-23  0:53   ` Brian Norris
2024-05-24  9:46     ` [EXT] " David Lin
2024-05-24 17:02       ` Brian Norris
2024-05-24 22:00         ` David Lin
2024-05-24 22:54           ` Brian Norris
2024-05-25  0:50             ` David Lin
2024-05-25 11:24               ` David Lin
2024-06-14  2:18               ` David Lin
2024-06-20 17:53               ` Brian Norris
2024-06-21  4:36                 ` David Lin
2024-07-01  1:12                   ` David Lin
2024-07-01 20:47                     ` Brian Norris
2024-07-02 11:23                       ` David Lin
2024-07-02 18:21                         ` Brian Norris
2024-04-18  6:06 ` [PATCH v10 2/2] wifi: mwifiex: add host mlme for AP mode David Lin
2024-05-23  0:59   ` Brian Norris
2024-05-23  2:20     ` [EXT] " David Lin
2024-06-12 13:11   ` Sascha Hauer
2024-06-14  2:06     ` [EXT] " David Lin
2024-06-14  6:31       ` Sascha Hauer
2024-06-17  2:15         ` David Lin
2024-06-17  6:29           ` Sascha Hauer
2024-06-17  7:44             ` David Lin
2024-04-18  6:47 ` [PATCH v10 0/2] wifi: mwifiex: add code to support host mlme Marcel Holtmann
2024-04-18  9:08   ` [EXT] " David Lin
2024-04-18  9:15     ` [EXT] " Marcel Holtmann
2024-04-19  4:00       ` David Lin
2024-04-19 21:42         ` Brian Norris
2024-04-22  8:34           ` David Lin
2024-04-23  2:29             ` David Lin
2024-04-24  8:11               ` Marcel Holtmann
2024-04-25  2:40                 ` David Lin
2024-04-26  1:08                   ` Brian Norris
2024-05-02  8:34                     ` David Lin
2024-05-13  1:27                       ` David Lin
2024-05-23  0:50                         ` Brian Norris [this message]
2024-04-26  1:00               ` Brian Norris
2024-04-26  3:04                 ` David Lin
2024-04-25  2:09             ` 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=Zk6S0m2U_xEojICb@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=marcel@holtmann.org \
    --cc=rafael.beims@toradex.com \
    --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).