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 6/6] arm64: dts: qcom: ipq9574: Add WiFi nodes for RDP433
Date: Wed, 23 Oct 2024 08:41:02 +0200 [thread overview]
Message-ID: <11d4fde9-ea5d-4abe-b43c-7c5c17d45ac2@kernel.org> (raw)
In-Reply-To: <20241023060352.605019-7-quic_rajkbhag@quicinc.com>
On 23/10/2024 08:03, Raj Kumar Bhagat wrote:
> The RDP433 is a Qualcomm Reference Design Platform based on the
> IPQ9574. It has three QCN9274 WiFi devices connected to PCIe1, PCIe2,
> and PCIe3. These devices are also connected among themselves via
> WSI connection. This WSI connection is essential to exchange control
> information among these devices
>
> The WSI connection in RDP433 is represented below:
>
> +-------+ +-------+ +-------+
> | pcie2 | | pcie3 | | pcie1 |
> | | | | | |
> +----->| wsi |------->| wsi |------->| wsi |-----+
> | | idx 0 | | idx 1 | | idx 2 | |
> | +-------+ +-------+ +-------+ |
> +------------------------------------------------------+
>
> Based on the above, the WSI properties for QCN9274 at pcie2 are:
> qcom,wsi-group-id = 0
> qcom,wsi-index = 0
> qcom,wsi-num-devices = 3;
>
> Hence, add WiFi nodes with WSI properties for all three QCN9274
> devices connected to RDP433.
>
> Signed-off-by: Raj Kumar Bhagat <quic_rajkbhag@quicinc.com>
> ---
> arch/arm64/boot/dts/qcom/ipq9574-rdp433.dts | 62 ++++++++++++++++++++-
> 1 file changed, 61 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/qcom/ipq9574-rdp433.dts b/arch/arm64/boot/dts/qcom/ipq9574-rdp433.dts
> index 165ebbb59511..2241e20ad42a 100644
> --- a/arch/arm64/boot/dts/qcom/ipq9574-rdp433.dts
> +++ b/arch/arm64/boot/dts/qcom/ipq9574-rdp433.dts
> @@ -3,7 +3,7 @@
> * IPQ9574 RDP433 board device tree source
> *
> * Copyright (c) 2020-2021 The Linux Foundation. All rights reserved.
> - * Copyright (c) 2023 Qualcomm Innovation Center, Inc. All rights reserved.
> + * Copyright (c) 2023-2024 Qualcomm Innovation Center, Inc. All rights reserved.
> */
>
> /dts-v1/;
> @@ -27,6 +27,26 @@ &pcie1 {
> perst-gpios = <&tlmm 26 GPIO_ACTIVE_LOW>;
> wake-gpios = <&tlmm 27 GPIO_ACTIVE_LOW>;
> status = "okay";
> +
> + pcie@0 {
> + device_type = "pci";
> + reg = <0x0 0x0 0x0 0x0 0x0>;
> + #address-cells = <3>;
> + #size-cells = <2>;
> + ranges;
> +
> + wifi1@0 {
> + compatible = "pci17cb,1109";
> + reg = <0x0 0x0 0x0 0x0 0x0>;
> + status = "okay";
Why?
> +
> + wsi {
> + qcom,wsi-group-id = <0>;
So all devices have the same group id? No other group id? So hard-code
it at 0?
> + qcom,wsi-index = <2>;
> + qcom,wsi-num-devices = <3>;
All this looks opposite how we organize usually DTS. Instead of phandles
you pass some sort of indices. Instead of re-using some existing
properties for remoteproc-related stuff, you add three more.
Best regards,
Krzysztof
prev parent reply other threads:[~2024-10-23 6:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 6:03 [RFC PATCH 0/6] wifi: ath12k: Add WSI node for QCN9274 in RDP433 for MLO Raj Kumar Bhagat
2024-10-23 6:03 ` [RFC PATCH 1/6] dt-bindings: net: wireless: update required properties for ath12k PCI module Raj Kumar Bhagat
2024-10-23 6:35 ` Krzysztof Kozlowski
2024-10-23 6:45 ` Raj Kumar Bhagat
2024-10-23 6:47 ` Krzysztof Kozlowski
2024-10-23 6:53 ` Raj Kumar Bhagat
2024-10-23 6:59 ` Krzysztof Kozlowski
2024-10-23 10:28 ` Raj Kumar Bhagat
2024-10-23 12:08 ` Krzysztof Kozlowski
2024-10-25 9:59 ` Raj Kumar Bhagat
2024-10-23 6:03 ` [RFC PATCH 2/6] dt-bindings: net: wireless: ath12k: describe WSI property for QCN9274 Raj Kumar Bhagat
2024-10-23 6:38 ` Krzysztof Kozlowski
2024-10-23 6:48 ` Krzysztof Kozlowski
2024-10-23 12:22 ` Raj Kumar Bhagat
2024-10-23 17:57 ` Krzysztof Kozlowski
2024-10-25 10:06 ` Raj Kumar Bhagat
2024-10-23 7:00 ` Krzysztof Kozlowski
2024-10-25 10:08 ` Raj Kumar Bhagat
2024-10-26 18:10 ` Krzysztof Kozlowski
2024-10-23 6:03 ` [RFC PATCH 3/6] wifi: ath12k: parse multiple device information from device tree Raj Kumar Bhagat
2024-10-23 6:39 ` Krzysztof Kozlowski
2024-10-23 6:03 ` [RFC PATCH 4/6] wifi: ath12k: Send partner device details in QMI MLO capability Raj Kumar Bhagat
2024-10-23 6:03 ` [RFC PATCH 5/6] wifi: ath12k: assign unique hardware link IDs during QMI host cap Raj Kumar Bhagat
2024-10-23 6:03 ` [RFC PATCH 6/6] arm64: dts: qcom: ipq9574: Add WiFi nodes for RDP433 Raj Kumar Bhagat
2024-10-23 6:41 ` Krzysztof Kozlowski [this message]
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=11d4fde9-ea5d-4abe-b43c-7c5c17d45ac2@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;
as well as URLs for NNTP newsgroup(s).