From: Krzysztof Kozlowski <krzk@kernel.org>
To: George Valkov <gvalkov@gmail.com>, Chen-Yu Tsai <wenst@chromium.org>
Cc: briannorris@chromium.org, johannes@sipsolutions.net,
andrew@lunn.ch, krzk+dt@kernel.org, francesco@dolcini.it,
johannes.berg@intel.com, kees@kernel.org,
miriam.rachel.korenblit@intel.com, 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,
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 v5 1/3] dt-bindings: net: wireless: add flag marvell,ignore-regulatory-hint
Date: Thu, 20 Aug 2026 10:14:26 +0200 [thread overview]
Message-ID: <c38cb98e-0746-4b28-b0c9-ce59e8338048@kernel.org> (raw)
In-Reply-To: <CADOrJmYxKTyDkKPaKCpH37RsyyZJZ+4uReE--+uvnHmEdNJVOw@mail.gmail.com>
On 20/08/2026 09:50, George Valkov wrote:
>
>
> Krzysztof:
>> regulatory-hint for me means usually regdb, but even with your meaning
>> you tell SW what to do - ignore hardware regulatory information.
>> Property should not tell what SW should do with hardware. Property
>> should tell what is happening here in the hardware. In this case: what
>> is the reason behind.
>>
>> IOW, why user of a board in country X, where regulatory data says X,
>> should have the correct regulatory data ignored?
>
> Because users in X buy a board for X and the regulatory data says U.
>
> Indeed when the ROM regulatory hint is set to US and the driver
> reports this to the OS, the wireless-regdb restrictions for US are
> applied. This would normally be fine, however the third radio in
> WRT3200ACM and WRT32x, reports US on all models including those sold
> in the EU and other non US markets. This creates a conflict with
> radios 0 and 1, which report FR and also with my correct setting: BG.
> With the wireless-regdb restrictions for US, FR and BG applied, radio
> 0 refuses to start.
So if you move with your router to US, you would need to change DTB?
IOW, the DTB is per user? This is obviously wrong... What if one device
has correct regulatory data written and you ignore it? Why would you
ignore it? If you decide to ignore correct regulatory data, then you can
as well ignore it unconditionally and this property is not needed.
>
> Would you approve any of these or suggest a better name for the flag?
> Should ROM be in upper or lower case?
> I omitted 'in-ROM' to keep it short, because the driver check line is
> already longer than 80 characters.
> - marvell,ignore-regulatory-hint (current)
> - marvell,ignore-regulatory-hint-in-ROM
> - marvell,invalid-regulatory-hint-in-ROM
> - marvell,invalid-regulatory-hint
> - marvell,invalid-regulatory-ROM
> - marvell,invalid-reg-hint-in-ROM
The point is that the regulatory hint is NOT INVALID. One device was
sold in US with US data, so how could it be invalid?
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-08-20 8:14 UTC|newest]
Thread overview: 36+ 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:39 ` [PATCH v3 1/2] wifi: mwifiex: ignore ROM regulatory hint on WRT3200ACM/WRT32x 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 ` [PATCH 2/3] ARM: dts: armada: WRT3200ACM: add marvell,ignore-regulatory-hint Georgi Valkov
2026-08-14 12:50 ` [PATCH 3/3] wifi: mwifiex: add dt flag to ignore incorrect ROM regulatory hint Georgi Valkov
2026-08-17 8:54 ` [PATCH 1/3] dt-bindings: net: wireless: add flag marvell,ignore-regulatory-hint Krzysztof Kozlowski
2026-08-17 10:43 ` George Valkov
2026-08-17 11:06 ` Krzysztof Kozlowski
2026-08-17 13:20 ` George Valkov
2026-08-17 13:24 ` Krzysztof Kozlowski
2026-08-17 13:48 ` George Valkov
2026-08-17 21:54 ` [PATCH v5 " Georgi Valkov
2026-08-17 21:54 ` [PATCH v5 2/3] ARM: dts: armada: WRT3200ACM: add marvell,ignore-regulatory-hint Georgi Valkov
2026-08-17 21:54 ` [PATCH v5 3/3] wifi: mwifiex: add dt flag to ignore incorrect ROM regulatory hint Georgi Valkov
2026-08-18 0:53 ` [PATCH v5 1/3] dt-bindings: net: wireless: add flag marvell,ignore-regulatory-hint Andrew Lunn
2026-08-18 9:58 ` George Valkov
2026-08-19 9:40 ` Krzysztof Kozlowski
2026-08-19 9:42 ` Krzysztof Kozlowski
2026-08-19 11:42 ` George Valkov
2026-08-19 12:26 ` Krzysztof Kozlowski
2026-08-20 6:42 ` Chen-Yu Tsai
2026-08-20 6:53 ` Krzysztof Kozlowski
2026-08-20 7:50 ` George Valkov
2026-08-20 8:14 ` Krzysztof Kozlowski [this message]
2026-08-20 9:33 ` George Valkov
2026-08-20 10:29 ` George 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=c38cb98e-0746-4b28-b0c9-ce59e8338048@kernel.org \
--to=krzk@kernel.org \
--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=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=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