From: Sven Eckelmann <se@simonwunderlich.de>
To: "Rob Herring (Arm)" <robh@kernel.org>
Cc: Lorenzo Bianconi <lorenzo@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Sean Wang <sean.wang@mediatek.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Johannes Berg <johannes@sipsolutions.net>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
Ryder Lee <ryder.lee@mediatek.com>, Felix Fietkau <nbd@nbd.name>,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-wireless@vger.kernel.org,
Shayne Chen <shayne.chen@mediatek.com>,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH mt76 v2 2/3] dt-bindings: net: wireless: mt76: introduce backoff limit properties
Date: Tue, 07 Oct 2025 10:07:52 +0200 [thread overview]
Message-ID: <2249324.Mh6RI2rZIc@ripper> (raw)
In-Reply-To: <175978385977.561952.12777844195936444721.robh@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1243 bytes --]
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@simonwunderlich.de>
> > ---
> > .../bindings/net/wireless/mediatek,mt76.yaml | 60 ++++++++++++++++++++++
> > 1 file changed, 60 insertions(+)
> >
>
> Reviewed-by: Rob Herring (Arm) <robh@kernel.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
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-10-07 8:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 10:04 [PATCH mt76 v2 0/3] wifi: mt76: mt7915: Beamforming backoff limit table Sven Eckelmann (Plasma Cloud)
2025-09-26 10:04 ` [PATCH mt76 v2 1/3] dt-bindings: net: wireless: mt76: Document power-limits country property Sven Eckelmann (Plasma Cloud)
2025-10-06 20:45 ` Rob Herring
2025-10-06 20:48 ` Johannes Berg
2025-10-07 7:56 ` Sven Eckelmann
2025-09-26 10:04 ` [PATCH mt76 v2 2/3] dt-bindings: net: wireless: mt76: introduce backoff limit properties Sven Eckelmann (Plasma Cloud)
2025-10-06 20:53 ` Rob Herring (Arm)
2025-10-07 8:07 ` Sven Eckelmann [this message]
2025-09-26 10:04 ` [PATCH mt76 v2 3/3] wifi: mt76: mt7915: add bf backoff limit table support Sven Eckelmann (Plasma Cloud)
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=2249324.Mh6RI2rZIc@ripper \
--to=se@simonwunderlich.de \
--cc=alexandre.torgue@foss.st.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=johannes@sipsolutions.net \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=nbd@nbd.name \
--cc=robh@kernel.org \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=shayne.chen@mediatek.com \
/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;
as well as URLs for NNTP newsgroup(s).