From: Baochen Qiang <baochen.qiang@oss.qualcomm.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>,
Jeff Johnson <jjohnson@kernel.org>,
Johannes Berg <johannes@sipsolutions.net>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
ath10k@lists.infradead.org, ath11k@lists.infradead.org,
devicetree@vger.kernel.org, ath12k@lists.infradead.org,
Miaoqing Pan <miaoqing.pan@oss.qualcomm.com>
Subject: Re: [PATCH 0/2] wifi: ath: Use static calibration variant table for devicetree platforms
Date: Mon, 17 Nov 2025 10:36:39 +0800 [thread overview]
Message-ID: <2fd84ab2-2e3e-4d05-add5-17930a35fedf@oss.qualcomm.com> (raw)
In-Reply-To: <20251114-ath-variant-tbl-v1-0-a9adfc49e3f3@oss.qualcomm.com>
On 11/14/2025 6:22 PM, Manivannan Sadhasivam wrote:
> Hi,
>
> This series aims to deprecate the usage of "qcom,*calibration-variant"
> devicetree property to select the calibration variant for the WLAN devices. This
> is necessary for WLAN devices connected using PCI bus, as hardcoding the device
> specific information in PCI devicetree node causes the node to be updated every
> time when a new device variant is attached to the PCI slot. This approach is not
> scalable and causes bad user experience.
I am not very clear about the problem here: is calibration variant device/module specific,
or platform specific? If it is module specific, why the lookup is based on the machine
'model' property? While if it is platform specific, why do we need to update devicetree
node whenever a new device is attached?
>
> So to avoid relying on the "qcom,*calibration-variant" property, this series
> introduces a new static calibration variant table based lookup. The newly
> introduced helper, ath_get_calib_variant() will parse the model name from
> devicetree and use it to do the variant lookup during runtime. The
> ath_calib_variant_table[] will hold all the model and calibration variant
> entries for the supported devices.
>
> Going forward, new entries will be added to this table to support calibration
> variants.
>
> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
> ---
> Manivannan Sadhasivam (2):
> wifi: ath: Use static calibration variant table for devicetree platforms
> dt-bindings: wireless: ath: Deprecate 'qcom,calibration-variant' property
>
> .../bindings/net/wireless/qcom,ath10k.yaml | 1 +
> .../bindings/net/wireless/qcom,ath11k-pci.yaml | 3 +-
> .../bindings/net/wireless/qcom,ath11k.yaml | 1 +
> .../bindings/net/wireless/qcom,ath12k-wsi.yaml | 6 +-
> .../bindings/net/wireless/qcom,ipq5332-wifi.yaml | 2 +-
> drivers/net/wireless/ath/ath.h | 98 ++++++++++++++++++++++
> drivers/net/wireless/ath/ath10k/core.c | 5 ++
> drivers/net/wireless/ath/ath11k/core.c | 7 ++
> 8 files changed, 115 insertions(+), 8 deletions(-)
> ---
> base-commit: 3a8660878839faadb4f1a6dd72c3179c1df56787
> change-id: 20251114-ath-variant-tbl-22865456a527
>
> Best regards,
next prev parent reply other threads:[~2025-11-17 2:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 10:22 [PATCH 0/2] wifi: ath: Use static calibration variant table for devicetree platforms Manivannan Sadhasivam
2025-11-14 10:22 ` [PATCH 1/2] " Manivannan Sadhasivam
2025-11-14 10:45 ` Krzysztof Kozlowski
2025-11-14 11:16 ` Manivannan Sadhasivam
2025-11-14 11:24 ` Krzysztof Kozlowski
2025-11-14 11:44 ` Srinivas Kandagatla
2025-11-14 11:48 ` Krzysztof Kozlowski
2025-11-15 9:51 ` kernel test robot
2025-11-14 10:22 ` [PATCH 2/2] dt-bindings: wireless: ath: Deprecate 'qcom,calibration-variant' property Manivannan Sadhasivam
2025-11-14 10:47 ` Krzysztof Kozlowski
2025-11-14 11:02 ` Manivannan Sadhasivam
2025-11-14 11:04 ` Krzysztof Kozlowski
2025-11-14 11:18 ` Manivannan Sadhasivam
2025-11-14 17:29 ` Jeff Johnson
2025-11-17 9:03 ` Manivannan Sadhasivam
2025-11-17 2:36 ` Baochen Qiang [this message]
2025-11-17 9:00 ` [PATCH 0/2] wifi: ath: Use static calibration variant table for devicetree platforms Manivannan Sadhasivam
2025-11-17 9:40 ` Baochen Qiang
2025-11-17 12:45 ` Manivannan Sadhasivam
2025-11-17 17:13 ` Jeff Johnson
2025-11-18 6:53 ` Manivannan Sadhasivam
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=2fd84ab2-2e3e-4d05-add5-17930a35fedf@oss.qualcomm.com \
--to=baochen.qiang@oss.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=ath11k@lists.infradead.org \
--cc=ath12k@lists.infradead.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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=manivannan.sadhasivam@oss.qualcomm.com \
--cc=miaoqing.pan@oss.qualcomm.com \
--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;
as well as URLs for NNTP newsgroup(s).