Re: [PATCH v5 1/3] dt-bindings: net: wireless: add flag marvell,ignore-regulatory-hint

[Krzysztof Kozlowski]

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