From: Georgi Valkov <gvalkov@gmail.com>
To: briannorris@chromium.org, johannes@sipsolutions.net, andrew@lunn.ch
Cc: 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,
error27@gmail.com, s.kerkmann@pengutronix.de,
gregory.clement@bootlin.com, sebastian.hesselbarth@gmail.com,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
Frank.Li@nxp.com, chunfan.chen@gmail.com,
linux-arm-kernel@lists.infradead.org,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, stable@vger.kernel.org,
gvalkov@gmail.com
Subject: [PATCH 2/3] ARM: dts: armada: WRT3200ACM: add marvell,ignore-regulatory-hint
Date: Fri, 14 Aug 2026 15:50:24 +0300 [thread overview]
Message-ID: <20260814125025.90522-2-gvalkov@gmail.com> (raw)
In-Reply-To: <20260814125025.90522-1-gvalkov@gmail.com>
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.
Add a flag marvell,ignore-regulatory-hint to the WRT3200ACM device-tree,
which signals mwifiex to ignore an incorrect regulatory hint from ROM,
so userspace can set the correct platform regulatory domain. The radios
in WRT3200ACM/WRT32x 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 Linux kernel sources do not have support for WRT32x. An equivalent
patch for these routers has to be sent to OpenWrt.
[1] https://github.com/kaloz/mwlwifi/issues/173#issuecomment-307879699
[2] https://github.com/openwrt/openwrt/issues/9956
Tested-on: WRT3200ACM, OpenWrt, make dt_binding_check: pass
Cc: stable@vger.kernel.org
Signed-off-by: Georgi Valkov <gvalkov@gmail.com>
---
arch/arm/boot/dts/marvell/armada-385-linksys-rango.dts | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/marvell/armada-385-linksys-rango.dts b/arch/arm/boot/dts/marvell/armada-385-linksys-rango.dts
index 4ab45f294de2..c5f94463ef71 100644
--- a/arch/arm/boot/dts/marvell/armada-385-linksys-rango.dts
+++ b/arch/arm/boot/dts/marvell/armada-385-linksys-rango.dts
@@ -165,6 +165,12 @@ &sdhci {
wp-inverted;
bus-width = <8>;
status = "okay";
+
+ wifi@1 {
+ compatible = "marvell,sd8897";
+ reg = <1>;
+ marvell,ignore-regulatory-hint;
+ };
};
&usb3_1_vbus {
--
2.55.0
next prev parent reply other threads:[~2026-08-14 12:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 10:35 [PATCH] wifi: mwifiex: ignore ROM regulatory hint on WRT3200ACM/WRT32x 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
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:43 ` sashiko-bot
2026-08-07 18:37 ` [PATCH v3 1/2] wifi: mwifiex: ignore ROM regulatory hint on WRT3200ACM/WRT32x sashiko-bot
2026-08-07 18:39 ` 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 ` Georgi Valkov [this message]
2026-08-14 13:00 ` [PATCH 2/3] ARM: dts: armada: WRT3200ACM: add marvell,ignore-regulatory-hint sashiko-bot
2026-08-14 12:50 ` [PATCH 3/3] wifi: mwifiex: add dt flag to ignore incorrect ROM regulatory hint Georgi 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=20260814125025.90522-2-gvalkov@gmail.com \
--to=gvalkov@gmail.com \
--cc=Frank.Li@nxp.com \
--cc=andrew@lunn.ch \
--cc=avraham.stern@intel.com \
--cc=briannorris@chromium.org \
--cc=chunfan.chen@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=error27@gmail.com \
--cc=francesco@dolcini.it \
--cc=gregory.clement@bootlin.com \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=kees@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.com \
--cc=rafael.beims@toradex.com \
--cc=robh@kernel.org \
--cc=s.kerkmann@pengutronix.de \
--cc=sebastian.hesselbarth@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.