From: Alexandru Gagniuc <mr.nuke.me@gmail.com>
To: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
jjohnson@kernel.org, ath11k@lists.infradead.org,
Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Alexandru Gagniuc <mr.nuke.me@gmail.com>
Subject: [PATCH 1/2] dt: bindings: net: ath11k: add IPQ9574 compatible
Date: Sun, 28 Dec 2025 09:58:51 -0600 [thread overview]
Message-ID: <20251228155855.2118792-2-mr.nuke.me@gmail.com> (raw)
In-Reply-To: <20251228155855.2118792-1-mr.nuke.me@gmail.com>
Add IPQ9574 device support for ath11k. The schema is identical to
ipq6018, so add the compatible string where needed.
Signed-off-by: Alexandru Gagniuc <mr.nuke.me@gmail.com>
---
.../devicetree/bindings/net/wireless/qcom,ath11k.yaml | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/net/wireless/qcom,ath11k.yaml b/Documentation/devicetree/bindings/net/wireless/qcom,ath11k.yaml
index c089677702cf1..8293ea29b723e 100644
--- a/Documentation/devicetree/bindings/net/wireless/qcom,ath11k.yaml
+++ b/Documentation/devicetree/bindings/net/wireless/qcom,ath11k.yaml
@@ -17,6 +17,7 @@ description: |
properties:
compatible:
enum:
+ - qcom,ipq9574-wifi
- qcom,ipq8074-wifi
- qcom,ipq6018-wifi
- qcom,wcn6750-wifi
@@ -102,6 +103,7 @@ allOf:
compatible:
contains:
enum:
+ - qcom,ipq9574-wifi
- qcom,ipq8074-wifi
- qcom,ipq6018-wifi
then:
@@ -220,6 +222,7 @@ allOf:
compatible:
contains:
enum:
+ - qcom,ipq9574-wifi
- qcom,ipq8074-wifi
- qcom,ipq6018-wifi
then:
--
2.45.1
next prev parent reply other threads:[~2025-12-28 15:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-28 15:58 [PATCH 0/2] ath11k: support IPQ9574 Alexandru Gagniuc
2025-12-28 15:58 ` Alexandru Gagniuc [this message]
2025-12-30 11:46 ` [PATCH 1/2] dt: bindings: net: ath11k: add IPQ9574 compatible Krzysztof Kozlowski
2025-12-28 15:58 ` [PATCH 2/2] wifi: ath11k: support ipq9574 Alexandru Gagniuc
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=20251228155855.2118792-2-mr.nuke.me@gmail.com \
--to=mr.nuke.me@gmail.com \
--cc=ath11k@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=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