From: Krzysztof Kozlowski <krzk@kernel.org>
To: Raj Kumar Bhagat <quic_rajkbhag@quicinc.com>, ath12k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org, Kalle Valo <kvalo@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jeff Johnson <jjohnson@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [RFC PATCH v3 0/5] wifi: ath12k: Add wifi device node with WSI for QCN9274 in RDP433
Date: Thu, 7 Nov 2024 11:23:20 +0100 [thread overview]
Message-ID: <49a6ec0d-8a0b-49aa-a9eb-1174cff930f6@kernel.org> (raw)
In-Reply-To: <20241105180444.770951-1-quic_rajkbhag@quicinc.com>
On 05/11/2024 19:04, Raj Kumar Bhagat wrote:
> The RDP433 is a Qualcomm Reference Design Platform based on the
> IPQ9574. It features three QCN9274 WiFi devices connected to PCIe1,
> PCIe2, and PCIe3. These devices are also interconnected via a WLAN
> Serial Interface (WSI) connection. This WSI connection is essential
> for exchanging control information among these devices.
>
> This patch series describes the WSI interface found in QCN9274 in
> device tree and uses this device tree node in the Ath12k driver to get the
> details of WSI connection for Multi Link Operation (MLO) among multiple
> QCN9274 devices.
>
> NOTES:
> 1. As ath12k MLO patches are not ready yet, this patchset does not apply
> to the ath.git ath-next branch and that's why the patchset is marked
> as RFC. These are the work-in-progress patches we have at the moment.
> The full set of MLO patches is available at:
> https://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git/log/?h=ath12k-mlo-qcn9274
>
> 2. The dependency marked below applies only to the DTS patch. The
> dt-bindings patches do not have this dependency.
>
> Depends-On: [PATCH V7 0/4] Add PCIe support for IPQ9574
> Link: https://lore.kernel.org/linux-pci/20240801054803.3015572-1-quic_srichara@quicinc.com/
>
> v3:
> - Created a separate binding "qcom,ath12k-wsi.yaml" to describe ath12k PCI
> devices with WSI interface.
Thanks for the changes. When you finish with testing/RFC, please send
proper version for review (just remember to keep numbering, next one is
v4 regardless whether this is RFC or not).
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-11-07 10:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 18:04 [RFC PATCH v3 0/5] wifi: ath12k: Add wifi device node with WSI for QCN9274 in RDP433 Raj Kumar Bhagat
2024-11-05 18:04 ` [RFC PATCH v3 1/5] dt-bindings: net: wireless: Describe ath12k PCI module with WSI Raj Kumar Bhagat
2024-11-07 17:36 ` Jeff Johnson
2024-12-20 20:03 ` Konrad Dybcio
2024-12-20 21:47 ` Jeff Johnson
2024-12-20 22:05 ` Konrad Dybcio
2024-12-20 22:05 ` Konrad Dybcio
2024-12-23 4:23 ` Raj Kumar Bhagat
2024-11-05 18:04 ` [RFC PATCH v3 2/5] wifi: ath12k: Parse multiple device information from device tree Raj Kumar Bhagat
2024-11-05 18:04 ` [RFC PATCH v3 3/5] wifi: ath12k: Send partner device details in QMI MLO capability Raj Kumar Bhagat
2024-11-05 18:04 ` [RFC PATCH v3 4/5] wifi: ath12k: Assign unique hardware link IDs during QMI host capability Raj Kumar Bhagat
2024-11-05 18:04 ` [RFC PATCH v3 5/5] arm64: dts: qcom: ipq9574: Add WiFi nodes for RDP433 Raj Kumar Bhagat
2024-11-07 10:23 ` Krzysztof Kozlowski [this message]
2024-11-07 11:06 ` [RFC PATCH v3 0/5] wifi: ath12k: Add wifi device node with WSI for QCN9274 in RDP433 Dmitry Baryshkov
2024-11-07 11:29 ` Krzysztof Kozlowski
2024-11-07 12:03 ` Dmitry Baryshkov
2024-11-07 12:16 ` Krzysztof Kozlowski
2024-11-07 13:20 ` Dmitry Baryshkov
2024-11-11 17:57 ` Kalle Valo
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=49a6ec0d-8a0b-49aa-a9eb-1174cff930f6@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=ath12k@lists.infradead.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jjohnson@kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_rajkbhag@quicinc.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