From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Lijuan Gao <quic_lijuang@quicinc.com>,
Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: kernel@quicinc.com, linux-arm-msm@vger.kernel.org,
linux-remoteproc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/6] arm64: dts: qcom: qcs615: Add IMEM and PIL info region
Date: Wed, 23 Apr 2025 11:30:16 +0200 [thread overview]
Message-ID: <b8bde418-450a-42ce-8d39-098d5c10e2a4@oss.qualcomm.com> (raw)
In-Reply-To: <20250423-add_qcs615_remoteproc_support-v1-4-a94fe8799f14@quicinc.com>
On 4/23/25 11:17 AM, Lijuan Gao wrote:
> Add a simple-mfd representing IMEM on QCS615 and define the PIL
> relocation info region, so that post mortem tools will be able
> to locate the loaded remoteprocs.
>
> Signed-off-by: Lijuan Gao <quic_lijuang@quicinc.com>
> ---
> arch/arm64/boot/dts/qcom/qcs615.dtsi | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/qcom/qcs615.dtsi b/arch/arm64/boot/dts/qcom/qcs615.dtsi
> index ab3c6ba5842b..fe9fda6b71c4 100644
> --- a/arch/arm64/boot/dts/qcom/qcs615.dtsi
> +++ b/arch/arm64/boot/dts/qcom/qcs615.dtsi
> @@ -3297,6 +3297,20 @@ sram@c3f0000 {
> reg = <0x0 0x0c3f0000 0x0 0x400>;
> };
>
> + sram@146aa000 {
> + compatible = "qcom,qcs615-imem", "syscon", "simple-mfd";
> + reg = <0x0 0x146aa000 0x0 0x1000>;
> + ranges = <0 0 0x146aa000 0x1000>;
IMEM is a lot bigger than what you describe here
Konrad
next prev parent reply other threads:[~2025-04-23 9:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 9:17 [PATCH 0/6] arm64: dts: qcom: qcs615: enable remoteprocs - ADSP and CDSP Lijuan Gao
2025-04-23 9:17 ` [PATCH 1/6] dt-bindings: remoteproc: qcom,sm8150-pas: Document QCS615 remoteproc Lijuan Gao
2025-04-28 7:48 ` Krzysztof Kozlowski
2025-04-23 9:17 ` [PATCH 2/6] dt-bindings: soc: qcom: add qcom,qcs615-imem compatible Lijuan Gao
2025-04-28 7:52 ` Krzysztof Kozlowski
2025-04-23 9:17 ` [PATCH 3/6] arm64: dts: qcom: qcs615: Add mproc node for SEMP2P Lijuan Gao
2025-04-23 9:29 ` Konrad Dybcio
2025-05-07 6:24 ` Lijuan Gao
2025-04-23 9:17 ` [PATCH 4/6] arm64: dts: qcom: qcs615: Add IMEM and PIL info region Lijuan Gao
2025-04-23 9:30 ` Konrad Dybcio [this message]
2025-04-23 9:17 ` [PATCH 5/6] arm64: dts: qcom: qcs615: add ADSP and CDSP nodes Lijuan Gao
2025-04-23 9:34 ` Konrad Dybcio
2025-04-24 7:56 ` Lijuan Gao
2025-04-26 9:54 ` Konrad Dybcio
2025-04-23 9:17 ` [PATCH 6/6] arm64: dts: qcom: qcs615-ride: enable remoteprocs Lijuan Gao
2025-04-23 13:40 ` Dmitry Baryshkov
2025-04-24 8:24 ` Lijuan Gao
2025-04-23 13:37 ` [PATCH 0/6] arm64: dts: qcom: qcs615: enable remoteprocs - ADSP and CDSP Rob Herring (Arm)
2025-04-24 8:05 ` Lijuan Gao
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=b8bde418-450a-42ce-8d39-098d5c10e2a4@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@quicinc.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mathieu.poirier@linaro.org \
--cc=quic_lijuang@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