From: Francesco Dolcini <francesco@dolcini.it>
To: David Lin <yu-hao.lin@nxp.com>, Sascha Hauer <s.hauer@pengutronix.de>
Cc: Brian Norris <briannorris@chromium.org>,
Francesco Dolcini <francesco@dolcini.it>,
Kalle Valo <kvalo@kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Pete Hsieh <tsung-hsien.hsieh@nxp.com>
Subject: Re: [EXT] [PATCH] wifi: mwifiex: Ensure all STA and AP use the same channel
Date: Mon, 9 Sep 2024 19:17:57 +0200 [thread overview]
Message-ID: <20240909171757.GA60827@francesco-nb> (raw)
In-Reply-To: <DU0PR04MB9636AF11600D2ABF286FA6EDD1932@DU0PR04MB9636.eurprd04.prod.outlook.com>
Hello Sascha,
On Tue, Sep 03, 2024 at 07:31:34AM +0000, David Lin wrote:
> > From: Sascha Hauer <s.hauer@pengutronix.de>
> >
> > The mwifiex chips support simultaneous Accesspoint and station mode, but this
> > only works when all are using the same channel. The downstream driver uses
> > ECSA which makes the Accesspoint automatically switch to the channel the
> > station is going to use. Until this is implemented in the mwifiex driver at
> > least catch this situation and bail out with an error.
> > Userspace doesn't have a meaningful way to figure out what went wrong, so
> > print an error message to give the user a clue.
> >
> > Without this patch the driver would timeout on the
> > HostCmd_CMD_802_11_ASSOCIATE command when creating a station with a
> > channel different from the one that an existing accesspoint uses.
> >
> > Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> > Cc: stable@vger.kernel.org
...
> Please use
> https://patchwork.kernel.org/project/linux-wireless/patch/20240902084311.2607-1-yu-hao.lin@nxp.com/
> to replace this patch.
>
> This patch can't let AP and STA running on the same channel if some
> wiphy parameters are set.
>
Sasha, any comment on this? It seems you are solving the same issue (I
did not look into any of the 2 patches myself so far).
Francesco
prev parent reply other threads:[~2024-09-09 17:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 6:56 [PATCH] wifi: mwifiex: Ensure all STA and AP use the same channel Sascha Hauer
2024-08-30 9:49 ` Kalle Valo
2024-08-30 11:04 ` Sascha Hauer
2024-08-30 11:58 ` Johannes Berg
2024-09-03 7:31 ` [EXT] " David Lin
2024-09-09 17:17 ` Francesco Dolcini [this message]
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=20240909171757.GA60827@francesco-nb \
--to=francesco@dolcini.it \
--cc=briannorris@chromium.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=stable@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