Re: [PATCH v6 1/3] dt-bindings: net: wireless: add flag marvell,invalid-reg-hint-in-rom
Krzysztof Kozlowski <[email protected]>
| Newsgroups | org.kernel.vger.linux-wireless,org.infradead.lists.linux-arm-kernel,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-kernel,org.kernel.vger.stable |
|---|---|
| Message-ID | <[email protected]> |
On 27/08/2026 15:08, George Valkov wrote: > On Thu, 27 Aug 2026 at 13:34, Krzysztof Kozlowski <[email protected]> wrote: >> >> On Fri, Aug 21, 2026 at 04:07:26AM +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 phy0 from starting on any DFS channel. phy2 works. >>> >>> Add a device-tree flag, which allows affected devices, where the radio >>> conflicts with the platform to ignore the incorrect regulatory hint in >>> the ROM of the radio, so the platform regulatory domain can be used. >>> This does not allow the user to change the regulatory configuration of >>> any radio. It only allows phy0 to start and operate according to its >>> certified configuration. >>> >>> [1] https://github.com/kaloz/mwlwifi/issues/173#issuecomment-307879699 >>> [2] https://github.com/openwrt/openwrt/issues/9956 >>> >>> Cc: [email protected] >> >> I don't think there is any bug to be fixed here. Support was incomplete, >> so you add a missing quirk, but there was no bug in the binding. >> Binding was correct. >> >> With stable dropped: >> >> Reviewed-by: Krzysztof Kozlowski <[email protected]> > > I added Reviewed-by to the first patch and sent v7 with these changes: > 1. drop Cc: stable, the first patch only documents a binding > 2. restore colon after Tested-on as requested by openwrt-ai Hm? You cannot test a binding. Please ignore completely openwrt-ai, it's apparently hallucinating. Anyway, OpenWRT process does not matter to upstream kernel. Best regards, Krzysztof