Re: [PATCH v7 2/3] wifi: mwifiex: add dt flag to avoid conflict with platform reg domain
George Valkov <[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 | <CADOrJmY5jZvn8zEu-jCntGChXSY9wRd3bsOy1GB0EWNTY9GK6Q@mail.gmail.com> |
On Thu, 27 Aug 2026 at 18:33, Krzysztof Kozlowski <[email protected]> wrote: > > On 27/08/2026 15:03, 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. > > > > The change affects only platforms which explicitly define this flag, 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 > > OK, so this comment from v6 was not about binding, but this is still > wrong - there is no such tag. Just make it a standard sentence. > > Do not introduce OpenWRT rules in to the upstream kernel. Dropped the invalid tag. I hope this is suitable: The change has been tested on OpenWrt and fixes the issue where phy0 does not start on WRT3200ACM-EU when a DFS channel is used I sent v8: https://lore.kernel.org/linux-wireless/[email protected]/T/#t Greetings! Georgi Valkov