From: Rosen Penev <rosenp@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jeff Johnson <jjohnson@kernel.org>,
Loic Poulain <loic.poulain@oss.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, devicetree@vger.kernel.org,
ath10k@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH] dt-bindings: net: wireless: qcom,ath10k: add PCI devices
Date: Tue, 10 Nov 2026 19:44:18 -0800 [thread overview]
Message-ID: <20261111034418.194610-1-rosenp@gmail.com> (raw)
ath10k PCI devices can be described as children of their PCI host
bridge, for example to supply the MAC address and calibration data
through nvmem cells. The only compatible for that was "qcom,ath10k",
but the generic PCI device schema requires a node under a PCI bus to
carry a "pciVVVV,DDDD" or "pciclass,..." compatible, so such nodes fail
validation.
Add the PCI vendor/device IDs handled by the ath10k PCI driver, as the
ath9k and ath11k PCI bindings already do.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
---
.../devicetree/bindings/net/wireless/qcom,ath10k.yaml | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/Documentation/devicetree/bindings/net/wireless/qcom,ath10k.yaml b/Documentation/devicetree/bindings/net/wireless/qcom,ath10k.yaml
index 0cb065265df4..992926ce5c5e 100644
--- a/Documentation/devicetree/bindings/net/wireless/qcom,ath10k.yaml
+++ b/Documentation/devicetree/bindings/net/wireless/qcom,ath10k.yaml
@@ -15,6 +15,15 @@ description:
properties:
compatible:
enum:
+ - pci0777,11ac # QCA988X (Ubiquiti branded)
+ - pci168c,003c # QCA988X
+ - pci168c,003e # QCA6174
+ - pci168c,0040 # QCA99X0
+ - pci168c,0041 # QCA6164
+ - pci168c,0042 # QCA9377
+ - pci168c,0046 # QCA9984
+ - pci168c,0050 # QCA9887
+ - pci168c,0056 # QCA9888
- qcom,ath10k # SDIO-based devices
- qcom,ipq4019-wifi
- qcom,wcn3990-wifi # SNoC-based devices
--
2.56.0
reply other threads:[~2026-11-11 3:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261111034418.194610-1-rosenp@gmail.com \
--to=rosenp@gmail.com \
--cc=ath10k@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=loic.poulain@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
all inboxes | Powered by JetHome®