linux-kernel - Re: [PATCH mt76 v2 2/3] dt-bindings: net: wireless: mt76: introduce backoff limit properties

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <2249324.Mh6RI2rZIc@ripper>
Date: Tue, 07 Oct 2025 10:07:52 +0200
From: Sven Eckelmann <se@...onwunderlich.de>
To: "Rob Herring (Arm)" <robh@...nel.org>
Cc: Lorenzo Bianconi <lorenzo@...nel.org>, Conor Dooley <conor+dt@...nel.org>,
 Maxime Coquelin <mcoquelin.stm32@...il.com>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Sean Wang <sean.wang@...iatek.com>,
 AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>,
 Alexandre Torgue <alexandre.torgue@...s.st.com>,
 Johannes Berg <johannes@...solutions.net>, devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org, linux-stm32@...md-mailman.stormreply.com,
 Ryder Lee <ryder.lee@...iatek.com>, Felix Fietkau <nbd@....name>,
 Matthias Brugger <matthias.bgg@...il.com>, linux-wireless@...r.kernel.org,
 Shayne Chen <shayne.chen@...iatek.com>, linux-arm-kernel@...ts.infradead.org,
 linux-mediatek@...ts.infradead.org
Subject:
 Re: [PATCH mt76 v2 2/3] dt-bindings: net: wireless: mt76: introduce backoff
 limit properties

On Monday, 6 October 2025 22:53:36 CEST Rob Herring (Arm) wrote:
> 
> On Fri, 26 Sep 2025 12:04:53 +0200, Sven Eckelmann (Plasma Cloud) wrote:
> > Introduce path backoff limit properties in mt76 binding in order to specify
> > beamforming and non-beamforming backoff limits for 802.11n/ac/ax.
> > 
> > Signed-off-by: Sven Eckelmann (Plasma Cloud) <se@...onwunderlich.de>
> > ---
> >  .../bindings/net/wireless/mediatek,mt76.yaml       | 60 ++++++++++++++++++++++
> >  1 file changed, 60 insertions(+)
> > 
> 
> Reviewed-by: Rob Herring (Arm) <robh@...nel.org>
> 
> Though I know nothing about this. Is there any reason why this is 
> all specific to mt76 rather than being common? Perhaps these settings 
> are all just part of the opaque "calibration data" in the QCom case?

Yes, everyone handles it differently and has different requirement for the 
actual provided data. Qcom has the calibration data, pre-calibration data, 
calibration files and pre-calibration files (which also needs variants for 
different devices or regions). But the actual interpretation of this "opaque" 
blob is secret and handled directly by their firmware. Don't let me get 
started with the (sometimes) embedded regdb in their calibration data.

Regards,
	Sven
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)