mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marcel Ziswiler <marcel.ziswiler@toradex.com>
To: "s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
	"kvalo@kernel.org" <kvalo@kernel.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"francesco@dolcini.it" <francesco@dolcini.it>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"briannorris@chromium.org" <briannorris@chromium.org>,
	"yu-hao.lin@nxp.com" <yu-hao.lin@nxp.com>
Subject: Re: [PATCH] wifi: mwifiex: increase max_num_akm_suites
Date: Tue, 11 Jun 2024 13:12:26 +0000	[thread overview]
Message-ID: <bd519d27dbe5c239d621072f96f67e371e552a74.camel@toradex.com> (raw)
In-Reply-To: <Zmaq-4whltVgrzCz@pengutronix.de>

Hi Sascha

On Mon, 2024-06-10 at 09:27 +0200, Sascha Hauer wrote:
> On Thu, Jun 06, 2024 at 12:25:48PM +0000, Kalle Valo wrote:
> > Sascha Hauer <s.hauer@pengutronix.de> wrote:
> > 
> > > The maximum number of AKM suites will be set to two if not specified by
> > > the driver. Set it to CFG80211_MAX_NUM_AKM_SUITES to let userspace
> > > specify up to ten AKM suites in the akm_suites array.
> > > 
> > > Without only the first two AKM suites will be used, further ones are
> > > ignored.
> > > 
> > > Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> > 
> > I assume you that you have also tested this on a real device, right?
> 
> Sure. It was tested with a MAYA-W161-00B module from u-blox with a IW416
> chipset.
> 
> BTW I haven't mentioned this, but It fixes the same problem as mentioned here:
> 
> https://lore.kernel.org/linux-kernel/20240523081428.2852276-1-s.hauer@pengutronix.de/T/

As we are also using the IW416 albeit from the MAYA-W160-00B module on our Verdin AM62, we were wondering about
the exact use case this patch helps solving. Could you reveal some more details around this? Thanks!

> Sascha

Cheers

Marcel

  reply	other threads:[~2024-06-11 13:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-30 13:01 Sascha Hauer
2024-06-06 12:25 ` Kalle Valo
2024-06-10  7:27   ` Sascha Hauer
2024-06-11 13:12     ` Marcel Ziswiler [this message]
2024-06-12 13:03       ` s.hauer
2024-06-20 18:05 ` Brian Norris
2024-06-21  8:48   ` Sascha Hauer
2024-06-21 19:16     ` Brian Norris
2024-07-16  9:10 ` Sascha Hauer
2024-07-30  8:48   ` Kalle Valo
2024-08-04  8:54 ` Kalle Valo

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=bd519d27dbe5c239d621072f96f67e371e552a74.camel@toradex.com \
    --to=marcel.ziswiler@toradex.com \
    --cc=briannorris@chromium.org \
    --cc=francesco@dolcini.it \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=s.hauer@pengutronix.de \
    --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

all inboxes | Powered by JetHome®