From: Krzysztof Kozlowski <krzk@kernel.org>
To: Gokul Sriram Palanisamy <gokul.sriram.p@oss.qualcomm.com>,
andersson@kernel.org, mathieu.poirier@linaro.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
konradybcio@kernel.org, quic_mmanikan@quicinc.com,
linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
devicetree@vger.kernel.org
Cc: quic_srichara@quicinc.com, vignesh.viswanathan@oss.qualcomm.com
Subject: Re: [PATCH V4 8/8] arm64: dts: qcom: ipq9574: add nodes to bring up q6
Date: Thu, 3 Apr 2025 16:51:57 +0200 [thread overview]
Message-ID: <69986326-acec-4032-b110-2f93362b3941@kernel.org> (raw)
In-Reply-To: <20250403120304.2345677-9-gokul.sriram.p@oss.qualcomm.com>
On 03/04/2025 14:03, Gokul Sriram Palanisamy wrote:
> From: Manikanta Mylavarapu <quic_mmanikan@quicinc.com>
>
> Enable nodes required for q6 remoteproc bring up.
>
> Signed-off-by: Manikanta Mylavarapu <quic_mmanikan@quicinc.com>
> Signed-off-by: Gokul Sriram Palanisamy <gokul.sriram.p@oss.qualcomm.com>
> ---
> arch/arm64/boot/dts/qcom/ipq9574.dtsi | 61 ++++++++++++++++++++++++++-
> 1 file changed, 60 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/qcom/ipq9574.dtsi b/arch/arm64/boot/dts/qcom/ipq9574.dtsi
> index db69bff41afa..11a1849ec50f 100644
> --- a/arch/arm64/boot/dts/qcom/ipq9574.dtsi
> +++ b/arch/arm64/boot/dts/qcom/ipq9574.dtsi
> @@ -3,7 +3,7 @@
> * IPQ9574 SoC device tree source
> *
> * Copyright (c) 2020-2021 The Linux Foundation. All rights reserved.
> - * Copyright (c) 2023-2024, Qualcomm Innovation Center, Inc. All rights reserved.
> + * Copyright (c) 2023-2025, Qualcomm Innovation Center, Inc. All rights reserved.
> */
>
> #include <dt-bindings/clock/qcom,apss-ipq.h>
> @@ -226,6 +226,11 @@ smem@4aa00000 {
> hwlocks = <&tcsr_mutex 3>;
> no-map;
> };
> +
> + q6_region: wcss@4ab00000 {
> + reg = <0x0 0x4ab00000 0x0 0x2b00000>;
> + no-map;
> + };
> };
>
> soc: soc@0 {
> @@ -1473,6 +1478,36 @@ top_glue-critical {
> };
> };
> };
> +
> + q6v5_wcss: remoteproc@cd00000 {
> + compatible = "qcom,ipq9574-wcss-sec-pil";
> + reg = <0x0cd00000 0x4040>;
So this obviously was never built tested :/
I don't understand why bindings and DTS is being changed after half a
year. You got already review and what you sent supposed to be complete.
Now, half a year later, you change both bindings and DTS thus:
1. What was the point of reviewing it that time? I will skip reviewing
next time and wait till your patchsets reach v4 or v8 and review only
then. This is not the first time for IPQ patches. It is actually pattern.
2. How released hardware can change within this timeframe?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-04-03 14:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 12:02 [PATCH V4 0/8] Add new driver for WCSS secure PIL loading Gokul Sriram Palanisamy
2025-04-03 12:02 ` [PATCH V4 1/8] firmware: qcom_scm: ipq5332: add support to pass metadata size Gokul Sriram Palanisamy
2025-04-04 22:41 ` Konrad Dybcio
2025-04-03 12:02 ` [PATCH V4 2/8] dt-bindings: remoteproc: qcom: document hexagon based WCSS secure PIL Gokul Sriram Palanisamy
2025-04-03 14:21 ` Krzysztof Kozlowski
2025-04-04 7:08 ` Gokul Sriram P
2025-04-14 4:47 ` Gokul Sriram P
2025-04-03 12:02 ` [PATCH V4 3/8] remoteproc: qcom: add hexagon based WCSS secure PIL driver Gokul Sriram Palanisamy
2025-04-03 12:03 ` [PATCH V4 4/8] soc: qcom: smem: introduce qcom_smem_get_machid() Gokul Sriram Palanisamy
2025-04-04 22:45 ` Konrad Dybcio
2025-04-07 5:00 ` Gokul Sriram P
2025-04-03 12:03 ` [PATCH V4 5/8] remoteproc: qcom: add support for Q6 device-tree loading Gokul Sriram Palanisamy
2025-04-03 12:03 ` [PATCH V4 6/8] arm64: dts: qcom: ipq5332: add nodes to bringup q6 Gokul Sriram Palanisamy
2025-04-03 12:03 ` [PATCH V4 7/8] arm64: dts: qcom: ipq5424: add nodes to bring up q6 Gokul Sriram Palanisamy
2025-04-03 14:23 ` Krzysztof Kozlowski
2025-04-03 12:03 ` [PATCH V4 8/8] arm64: dts: qcom: ipq9574: " Gokul Sriram Palanisamy
2025-04-03 14:51 ` Krzysztof Kozlowski [this message]
2025-04-04 7:18 ` Gokul Sriram P
2025-04-03 14:20 ` [PATCH V4 0/8] Add new driver for WCSS secure PIL loading Krzysztof Kozlowski
2025-04-03 14:35 ` Rob Herring (Arm)
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=69986326-acec-4032-b110-2f93362b3941@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gokul.sriram.p@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=quic_mmanikan@quicinc.com \
--cc=quic_srichara@quicinc.com \
--cc=robh@kernel.org \
--cc=vignesh.viswanathan@oss.qualcomm.com \
/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