Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Georgi Valkov <gvalkov@gmail.com>,
	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, rongqianfeng@vivo.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
Subject: Re: [PATCH v7 2/3] wifi: mwifiex: add dt flag to avoid conflict with platform reg domain
Date: Thu, 27 Aug 2026 17:33:02 +0200	[thread overview]
Message-ID: <fbde1932-5433-48e8-b352-bf27eb545149@kernel.org> (raw)
In-Reply-To: <20260827130335.6606-2-gvalkov@gmail.com>

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.

Best regards,
Krzysztof


  reply	other threads:[~2026-08-27 15:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-27 13:03 [PATCH v7 1/3] dt-bindings: net: wireless: add flag marvell,invalid-reg-hint-in-rom Georgi Valkov
2026-08-27 13:03 ` [PATCH v7 2/3] wifi: mwifiex: add dt flag to avoid conflict with platform reg domain Georgi Valkov
2026-08-27 15:33   ` Krzysztof Kozlowski [this message]
2026-08-27 17:27     ` George Valkov
2026-08-27 21:32       ` Krzysztof Kozlowski
2026-08-27 13:03 ` [PATCH v7 3/3] ARM: dts: armada: WRT3200ACM: add marvell,invalid-reg-hint-in-rom 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=fbde1932-5433-48e8-b352-bf27eb545149@kernel.org \
    --to=krzk@kernel.org \
    --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=gvalkov@gmail.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=rongqianfeng@vivo.com \
    --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