From: Baochen Qiang <baochen.qiang@oss.qualcomm.com>
To: Andrew LaMarche <andrewjlamarche@gmail.com>,
Johannes Berg <johannes@sipsolutions.net>,
Jeff Johnson <jjohnson@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-wireless@vger.kernel.org, devicetree@vger.kernel.org,
ath12k@lists.infradead.org, linux-kernel@vger.kernel.org,
Ernest Van Hoecke <ernestvanhoecke@gmail.com>
Subject: Re: [PATCH v2 1/2] wifi: ath12k: support calibration-variant from device tree
Date: Tue, 1 Sep 2026 09:52:36 +0800 [thread overview]
Message-ID: <5d6fab0d-e31d-4a81-a592-30ee1c6f295b@oss.qualcomm.com> (raw)
In-Reply-To: <20260630133001.1426824-1-andrewjlamarche@gmail.com>
On 6/30/2026 9:30 PM, Andrew LaMarche wrote:
> ath10k and ath11k support reading calibration variants from the device
> tree to locate the correct Board Description File (BDF). The ath12k-wsi
> binding already describes using qcom,calibration-variant but it is not
> implemented in the driver.
>
> Many ath12k designs expose all the radios under a single phy, each of
> which typically require a separate BDF. Without this, the radios may not
> come up or will not be calibrated correctly.
>
> Fix this by parsing the device tree for the generation-agnostic
> qcom,calibration-variant. This allows the driver to properly select,
> read and apply the correct BDF.
>
> Signed-off-by: Andrew LaMarche <andrewjlamarche@gmail.com>
Reviewed-by: Baochen Qiang <baochen.qiang@oss.qualcomm.com>
next prev parent reply other threads:[~2026-09-01 1:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 13:30 [PATCH v2 1/2] wifi: ath12k: support calibration-variant from device tree Andrew LaMarche
2026-06-30 13:30 ` [PATCH v2 2/2] dt-bindings: wireless: ath12k: drop qcom,ath12k-calibration-variant Andrew LaMarche
2026-07-01 7:05 ` Krzysztof Kozlowski
2026-07-02 9:32 ` [PATCH v2 1/2] wifi: ath12k: support calibration-variant from device tree Baochen Qiang
2026-08-31 19:41 ` Jeff Johnson
2026-08-31 20:09 ` Jeff Johnson
2026-09-01 1:52 ` Baochen Qiang
2026-09-01 1:52 ` Baochen Qiang [this message]
2026-09-01 12:32 ` Rameshkumar Sundaram
2026-09-03 19:02 ` Jeff Johnson
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=5d6fab0d-e31d-4a81-a592-30ee1c6f295b@oss.qualcomm.com \
--to=baochen.qiang@oss.qualcomm.com \
--cc=andrewjlamarche@gmail.com \
--cc=ath12k@lists.infradead.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ernestvanhoecke@gmail.com \
--cc=jjohnson@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=robh@kernel.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