From: Gokul Sriram P <gokul.sriram.p@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
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 2/8] dt-bindings: remoteproc: qcom: document hexagon based WCSS secure PIL
Date: Fri, 4 Apr 2025 12:38:43 +0530 [thread overview]
Message-ID: <91bba481-5871-48dc-a7d6-86f3bcb60d0d@oss.qualcomm.com> (raw)
In-Reply-To: <6b33d7ea-4ad5-454f-bd26-0ef961cf7ae3@kernel.org>
On 4/3/2025 7:51 PM, Krzysztof Kozlowski wrote:
> On 03/04/2025 14:02, Gokul Sriram Palanisamy wrote:
>> + minItems: 1
>> + items:
>> + - description: Q6 reserved region
>> + - description: Q6 dtb reserved region
>> +
>> + qcom,q6-dtb-info:
>> + $ref: /schemas/types.yaml#/definitions/phandle-array
> NAK, you added new properties which invalidates review. You must drop
> review after making such significant changes (3 new properties? Several
> other changed).
> See submitting patches.
>
> Anyway, NAK for the property, you don't get DTB info from DTB.
Sorry for the confusion. My bad, this Q6 DTB loading from rproc is a new
topic.
The HW/FW has not changed, will revert.
I will repost V5 with just the comments from V3 addressed and introduce
the changes
required for Q6 DTB in a separate series. Is that fine ?
Regards,
Gokul
next prev parent reply other threads:[~2025-04-04 7:08 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 [this message]
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
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=91bba481-5871-48dc-a7d6-86f3bcb60d0d@oss.qualcomm.com \
--to=gokul.sriram.p@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.