From: Rosen Penev <rosenp@gmail.com>
To: linux-wireless@vger.kernel.org
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
nbd@ndb.name, "Johannes Berg" <johannes@sipsolutions.net>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND
FLATTENED DEVICE TREE BINDINGS),
linux-kernel@vger.kernel.org (open list),
linux-mips@vger.kernel.org (open list:MIPS)
Subject: [PATCHv3 3/5] dt-bindings: net: wireless: ath9k: add WIFI bindings
Date: Thu, 22 May 2025 23:32:05 -0700 [thread overview]
Message-ID: <20250523063207.10040-4-rosenp@gmail.com> (raw)
In-Reply-To: <20250523063207.10040-1-rosenp@gmail.com>
These are for the wireless chips that come built in with various
Atheros/QCA SoCs. dts wise, the difference between pcie and the wmac is
AHB > PCIE > WIFI
AHB > WIFI
These will be used to replace the platform_device code with OF in the
following patch.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
---
.../bindings/net/wireless/qca,ath9k.yaml | 20 ++++++++++++++++++-
1 file changed, 19 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/net/wireless/qca,ath9k.yaml b/Documentation/devicetree/bindings/net/wireless/qca,ath9k.yaml
index 0e5412cff2bc..af2d01d3df23 100644
--- a/Documentation/devicetree/bindings/net/wireless/qca,ath9k.yaml
+++ b/Documentation/devicetree/bindings/net/wireless/qca,ath9k.yaml
@@ -12,7 +12,7 @@ maintainers:
description: |
This node provides properties for configuring the ath9k wireless device.
The node is expected to be specified as a child node of the PCI controller
- to which the wireless chip is connected.
+ or AHB bus to which the wireless chip is connected.
allOf:
- $ref: ieee80211.yaml#
@@ -35,6 +35,12 @@ properties:
- pci168c,0034 # AR9462
- pci168c,0036 # AR9565
- pci168c,0037 # AR1111 and AR9485
+ - qcom,ar9130-wifi
+ - qcom,ar9330-wifi
+ - qcom,ar9340-wifi
+ - qcom,qca9530-wifi
+ - qcom,qca9550-wifi
+ - qcom,qca9560-wifi
reg:
maxItems: 1
@@ -88,3 +94,15 @@ examples:
nvmem-cell-names = "mac-address", "calibration";
};
};
+ - |
+ ahb {
+ compatible = "simple-bus";
+ ranges;
+
+ wifi@180c0000 {
+ compatible = "qca,ar9130-wifi";
+ reg = <0x180c0000 0x230000>;
+
+ interrupts = <2>;
+ };
+ };
--
2.49.0
next prev parent reply other threads:[~2025-05-23 6:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 6:32 [PATCHv3 0/5] wifi: ath9k: add ahb OF support Rosen Penev
2025-05-23 6:32 ` [PATCHv3 1/5] wifi: ath9k: ahb: reorder declarations Rosen Penev
2025-05-23 6:32 ` [PATCHv3 2/5] wifi: ath9k: ahb: reorder includes Rosen Penev
2025-05-23 6:32 ` Rosen Penev [this message]
2025-05-23 6:42 ` [PATCHv3 3/5] dt-bindings: net: wireless: ath9k: add WIFI bindings Krzysztof Kozlowski
2025-05-24 4:18 ` Rosen Penev
2025-05-23 7:34 ` Rob Herring (Arm)
2025-05-23 6:32 ` [PATCHv3 4/5] wifi: ath9k: ahb: replace id_table with of Rosen Penev
2025-05-23 6:32 ` [PATCHv3 5/5] mips: dts: qca: add wmac support Rosen Penev
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=20250523063207.10040-4-rosenp@gmail.com \
--to=rosenp@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=johannes@sipsolutions.net \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@ndb.name \
--cc=robh@kernel.org \
--cc=toke@toke.dk \
--cc=tsbogend@alpha.franken.de \
/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).