From: Georgi Valkov <gvalkov@gmail.com>
To: briannorris@chromium.org, johannes@sipsolutions.net,
andrew@lunn.ch, krzk+dt@kernel.org
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, conor+dt@kernel.org, Frank.Li@nxp.com,
chunfan.chen@gmail.com, arend.vanspriel@broadcom.com,
peddolla.reddy@oss.qualcomm.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 v6 3/3] ARM: dts: armada: WRT3200ACM: add marvell,invalid-reg-hint-in-rom
Date: Fri, 21 Aug 2026 04:07:28 +0300 [thread overview]
Message-ID: <20260821010728.45065-3-gvalkov@gmail.com> (raw)
In-Reply-To: <20260821010728.45065-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 phy0 from starting on any DFS channel. phy2 works.
Add a flag marvell,invalid-reg-hint-in-rom to the WRT3200ACM device-tree,
which signals mwifiex that its regulatory hint from ROM conflicts with
the platform and should be ignored, so the platform regulatory domain can
be used. This does not allow the user to change the regulatory config of
any radio. It only allows phy0 to start and operate according to its
certified configuration. All radios in WRT3200ACM/WRT32x are locked to
the hard-coded configuration for which they are certified.
On WRT3200ACM, the platform configuration is stored on the devinfo mtd3
partition, which is read-only: cert_region=EU modelNumber=WRT3200ACM-EU
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
Cc: stable@vger.kernel.org
Signed-off-by: Georgi Valkov <gvalkov@gmail.com>
---
arch/arm/boot/dts/marvell/armada-385-linksys-rango.dts | 9 +++++++++
1 file changed, 9 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..2bf29981a031 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,15 @@ &sdhci {
wp-inverted;
bus-width = <8>;
status = "okay";
+
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ wifi@1 {
+ compatible = "marvell,sd8897";
+ reg = <1>;
+ marvell,invalid-reg-hint-in-rom;
+ };
};
&usb3_1_vbus {
--
2.55.0
prev parent reply other threads:[~2026-08-21 1:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 1:07 [PATCH v6 1/3] dt-bindings: net: wireless: add flag marvell,invalid-reg-hint-in-rom Georgi Valkov
2026-08-21 1:07 ` [PATCH v6 2/3] wifi: mwifiex: add dt flag to avoid conflict with platform reg domain Georgi Valkov
2026-08-21 1:07 ` Georgi Valkov [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=20260821010728.45065-3-gvalkov@gmail.com \
--to=gvalkov@gmail.com \
--cc=Frank.Li@nxp.com \
--cc=andrew@lunn.ch \
--cc=arend.vanspriel@broadcom.com \
--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=peddolla.reddy@oss.qualcomm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox