From: Jeff Chen <chunfan.chen@gmail.com>
To: Georgi Valkov <gvalkov@gmail.com>
Cc: briannorris@chromium.org, chunfan.chen@gmail.com,
francesco@dolcini.it, johannes.berg@intel.com, kees@kernel.org,
miriam.rachel.korenblit@intel.com, wenst@chromium.org,
rafael.beims@toradex.com, avraham.stern@intel.com,
peddolla.reddy@oss.qualcomm.com, error27@gmail.com,
s.kerkmann@pengutronix.de, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] wifi: mwifiex: ignore ROM regulatory hint on WRT3200ACM/WRT32x
Date: Fri, 7 Aug 2026 16:26:23 +0800 [thread overview]
Message-ID: <anWWr80yAcOQaVVS@nxpwireless-Inspiron-14-Plus-7440> (raw)
In-Reply-To: <20260731063118.26171-1-gvalkov@gmail.com>
On Fri, Jul 31, 2026 at 09:31:18 AM +0300, Georgi Valkov wrote:
> WRT3200ACM and WRT32x routers always report a fixed US regulatory domain
> from the mwifiex ROM, which conflicts with the platform regulatory
> configuration on units sold outside the US market. For example:
> - phy0 mwlwifi 5 GHz, hard-coded region 98 EU mapped to FR
> - phy1 mwlwifi 2.4 GHz, hard-coded region 98 EU mapped to FR
> - phy2 mwifiex 2.4 and 5 GHz, hard-coded region US
>
> When the system boots, it detects a conflict between the user selected
> region and the radios, e.g. BG FR US, and applies extreme restrictions,
> preventing use of 5 GHz and DFS channels. This also affects phy0.
>
> Ignore the incorrect regulatory hint in the ROM of these devices, so
> userspace can set the correct platform regulatory domain. These radios
> are locked to the hard-coded configuration for which they are certified,
> so the only impact is that the region conflict is avoided and the 5 GHz
> radios can be used.
>
> The change affects only WRT3200ACM and WRT32x routers, and helps
> overcome the incorrect behaviour of proprietary radio firmware.
>
> [1] https://github.com/kaloz/mwlwifi/issues/173#issuecomment-307879699
> [2] https://github.com/openwrt/openwrt/issues/9956
>
> Tested-on: WRT3200ACM, OpenWrt
> Cc: stable@vger.kernel.org
> Signed-off-by: Georgi Valkov <gvalkov@gmail.com>
> ---
Hi Georgi,
Thanks for the V2. The updated strings now match both environments.
However, checking board-specific DT strings inside a generic peripheral driver
is still not a good idea.
Since you asked about a better approach, why not consider the solution
mentioned by openwrt-ai using the "reg_alpha2" module parameter?
If OpenWrt injects "reg_alpha2=00" via a modprobe conf file under
target/linux/mvebu/, the ROM regulatory hint can be overridden from userspace
without needing any hardcoded logic inside the upstream driver.
Best regards,
Jeff
next prev parent reply other threads:[~2026-08-07 8:26 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 10:35 [PATCH] " Georgi Valkov
2026-07-30 2:16 ` Jeff Chen
2026-07-30 3:06 ` George Valkov
2026-07-30 3:24 ` George Valkov
2026-07-30 7:47 ` Jeff Chen
2026-07-31 6:31 ` [PATCH v2] " Georgi Valkov
2026-08-07 8:26 ` Jeff Chen [this message]
2026-08-07 18:21 ` [PATCH v3 1/2] " Georgi Valkov
2026-08-07 18:21 ` [PATCH v3 2/2] ARM: dts: armada: WRT3200ACM: add marvell,ignore-regulatory-hint Georgi Valkov
2026-08-07 18:39 ` [PATCH v3 1/2] wifi: mwifiex: ignore ROM regulatory hint on WRT3200ACM/WRT32x Johannes Berg
2026-08-07 19:49 ` George Valkov
2026-08-10 18:30 ` Brian Norris
2026-08-14 12:50 ` [PATCH 1/3] dt-bindings: net: wireless: add flag marvell,ignore-regulatory-hint Georgi Valkov
2026-08-14 12:50 ` [PATCH 2/3] ARM: dts: armada: WRT3200ACM: add marvell,ignore-regulatory-hint Georgi Valkov
2026-08-14 12:50 ` [PATCH 3/3] wifi: mwifiex: add dt flag to ignore incorrect ROM regulatory hint Georgi Valkov
2026-08-17 8:54 ` [PATCH 1/3] dt-bindings: net: wireless: add flag marvell,ignore-regulatory-hint Krzysztof Kozlowski
2026-08-17 10:43 ` George Valkov
2026-08-17 11:06 ` Krzysztof Kozlowski
2026-08-17 13:20 ` George Valkov
2026-08-17 13:24 ` Krzysztof Kozlowski
2026-08-17 13:48 ` George Valkov
2026-08-17 21:54 ` [PATCH v5 " Georgi Valkov
2026-08-17 21:54 ` [PATCH v5 2/3] ARM: dts: armada: WRT3200ACM: add marvell,ignore-regulatory-hint Georgi Valkov
2026-08-17 21:54 ` [PATCH v5 3/3] wifi: mwifiex: add dt flag to ignore incorrect ROM regulatory hint Georgi Valkov
2026-08-18 0:53 ` [PATCH v5 1/3] dt-bindings: net: wireless: add flag marvell,ignore-regulatory-hint Andrew Lunn
2026-08-18 9:58 ` George Valkov
2026-08-19 9:40 ` Krzysztof Kozlowski
2026-08-19 9:42 ` Krzysztof Kozlowski
2026-08-19 11:42 ` George Valkov
2026-08-19 12:26 ` Krzysztof Kozlowski
2026-08-20 6:42 ` Chen-Yu Tsai
2026-08-20 6:53 ` Krzysztof Kozlowski
2026-08-20 7:50 ` George Valkov
2026-08-20 8:14 ` Krzysztof Kozlowski
2026-08-20 9:33 ` George Valkov
2026-08-20 10:29 ` George Valkov
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=anWWr80yAcOQaVVS@nxpwireless-Inspiron-14-Plus-7440 \
--to=chunfan.chen@gmail.com \
--cc=avraham.stern@intel.com \
--cc=briannorris@chromium.org \
--cc=error27@gmail.com \
--cc=francesco@dolcini.it \
--cc=gvalkov@gmail.com \
--cc=johannes.berg@intel.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.com \
--cc=peddolla.reddy@oss.qualcomm.com \
--cc=rafael.beims@toradex.com \
--cc=s.kerkmann@pengutronix.de \
--cc=stable@vger.kernel.org \
--cc=wenst@chromium.org \
/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®