public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: David Lin <yu-hao.lin@nxp.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"briannorris@chromium.org" <briannorris@chromium.org>,
	"kvalo@kernel.org" <kvalo@kernel.org>,
	"francesco@dolcini.it" <francesco@dolcini.it>,
	Pete Hsieh <tsung-hsien.hsieh@nxp.com>
Subject: Re: [EXT] Re: [PATCH v2] wifi: mwifiex: avoid AP and STA running on different channel
Date: Tue, 10 Sep 2024 10:07:46 +0200	[thread overview]
Message-ID: <Zt_-Uo7AyMmrnXnJ@pengutronix.de> (raw)
In-Reply-To: <PA4PR04MB9638D57A9623D1B33C802EF9D19A2@PA4PR04MB9638.eurprd04.prod.outlook.com>

On Tue, Sep 10, 2024 at 07:28:29AM +0000, David Lin wrote:
> > From: Sascha Hauer <s.hauer@pengutronix.de>
> > Sent: Tuesday, September 10, 2024 3:22 PM
> > To: David Lin <yu-hao.lin@nxp.com>
> > Cc: linux-wireless@vger.kernel.org; linux-kernel@vger.kernel.org;
> > briannorris@chromium.org; kvalo@kernel.org; francesco@dolcini.it; Pete
> > Hsieh <tsung-hsien.hsieh@nxp.com>
> > Subject: Re: [EXT] Re: [PATCH v2] wifi: mwifiex: avoid AP and STA running on
> > different channel
> > 
> > Caution: This is an external email. Please take care when clicking links or
> > opening attachments. When in doubt, report the message using the 'Report
> > this email' button
> > 
> > 
> > On Tue, Sep 10, 2024 at 06:18:57AM +0000, David Lin wrote:
> > > > > > > > With DRCS support enabled AP and STA actually can run on
> > > > > > > > different channels with the current code. You are breaking
> > > > > > > > this scenario with this
> > > > > > patch.
> > > > > > > >
> > > > > > > > Sascha
> > > > > > > >
> > > > > > >
> > > > > > > DRCS will be checked in the future.
> > > > > >
> > > > > > By future you mean v3 of this patch?
> > > > > >
> > > > > > Sascha
> > > > > >
> > > > >
> > > > > No schedule now.
> > > >
> > > > I am getting confused now. You want us to abandon my patch in favour
> > > > of yours, but you have no plans to update your patch to avoid a
> > > > regression that you introduce with your patch?
> > > >
> > > > Sascha
> > > >
> > >
> > > My patch resolves the same issue as your patch. But your patch can't
> > > let AP and STA run on the same channel if some wiphy parameters are
> > > set.
> > >
> > > I wonder did you test your patch?
> > 
> > I finally see what you mean with "some wiphy parameters are set".
> > I did test my patch and I didn't run into this issue, because I haven't set
> > anything like rts_threshold in my config.
> > 
> > Nevertheless what I am trying to tell you in this thread is: Your patch
> > introduces a regression and needs an update.
> > 
> > It's not about my patch or your patch, both are currently not suitable for
> > inclusion and the question is: will you update your patch?
> > 
> > Sascha
> > 
> 
> Without DRCS, this patch can avoid firmware crash and this is the
> current plan for Mwifiex.  It won't affect any existing features.

What I am trying to tell you: Your patch fixes one thing and breaks
another.

The current mwifiex driver *does* support DRCS when enabled with the
drcs=1 module parameter. With DRCS enabled the current driver *can*
successfully run an Accesspoint on one channel and a station on another
channel. You are breaking this with your patch.

Your mwifiex_is_channel_setting_allowable() needs this:

        if (adapter->drcs_enabled)
		return true;

Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2024-09-10  8:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-02  8:43 [PATCH v2] wifi: mwifiex: avoid AP and STA running on different channel David Lin
2024-09-02  9:38 ` Sascha Hauer
2024-09-02 10:35   ` [EXT] " David Lin
2024-09-09 20:33     ` Sascha Hauer
2024-09-10  1:55       ` David Lin
2024-09-10  5:55         ` Sascha Hauer
2024-09-10  5:56           ` David Lin
2024-09-10  6:06             ` Sascha Hauer
2024-09-10  6:18               ` David Lin
2024-09-10  7:21                 ` Sascha Hauer
2024-09-10  7:28                   ` David Lin
2024-09-10  8:07                     ` Sascha Hauer [this message]
2024-09-10  8:21                       ` David Lin
2024-09-09 21:05 ` Sascha Hauer
2024-09-10  1:52   ` [EXT] " David Lin
2024-09-10  8:00     ` Sascha Hauer
2024-09-10  8:19       ` David Lin
2024-09-10  8:31         ` Sascha Hauer
2024-09-10  8:35           ` 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=Zt_-Uo7AyMmrnXnJ@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --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=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