devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Kathiravan Thirumoorthy
	<kathiravan.thirumoorthy@oss.qualcomm.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/6] arm64: dts: qcom: ipq8074: Add the IMEM node
Date: Tue, 8 Jul 2025 08:47:08 +0200	[thread overview]
Message-ID: <e7ad63b7-523d-4193-97b8-d33601de78f6@kernel.org> (raw)
In-Reply-To: <20250708-imem-v2-2-692eb92b228e@oss.qualcomm.com>

On 08/07/2025 07:39, Kathiravan Thirumoorthy wrote:
> Add the IMEM node to the device tree to extract debugging information
> like system restart reason, which is populated via IMEM. Define the
> IMEM region to enable this functionality.
> 
> As described, overall IMEM region is 24KB but only initial 4KB is
> accessible by all masters in the SoC.
> 
> Signed-off-by: Kathiravan Thirumoorthy <kathiravan.thirumoorthy@oss.qualcomm.com>
> ---
> Changes in v2:
> - Rounded off the size to 0x6000 (Konrad)
> ---
>  arch/arm64/boot/dts/qcom/ipq8074.dtsi | 9 +++++++++
>  1 file changed, 9 insertions(+)
> 
> diff --git a/arch/arm64/boot/dts/qcom/ipq8074.dtsi b/arch/arm64/boot/dts/qcom/ipq8074.dtsi
> index fffb47ec244899cf45984adbe8c4f9820bef5c5f..2ba07a02c222958b924c5bc178ac67f955088f7a 100644
> --- a/arch/arm64/boot/dts/qcom/ipq8074.dtsi
> +++ b/arch/arm64/boot/dts/qcom/ipq8074.dtsi
> @@ -625,6 +625,15 @@ qpic_nand: nand-controller@79b0000 {
>  			status = "disabled";
>  		};
>  
> +		sram@8600000 {
> +			compatible = "qcom,ipq8074-imem", "syscon", "simple-mfd";


It is still not simple-mfd. You should post complete node with children
or do not make it a simple-mfd.

Best regards,
Krzysztof

  reply	other threads:[~2025-07-08  6:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-08  5:39 [PATCH v2 0/6] Describe the IMEM present in Qualcomm IPQ SoC's Kathiravan Thirumoorthy
2025-07-08  5:39 ` [PATCH v2 1/6] dt-bindings: sram: qcom,imem: Document Qualcomm IPQ SoC's IMEM compatibles Kathiravan Thirumoorthy
2025-07-08  5:39 ` [PATCH v2 2/6] arm64: dts: qcom: ipq8074: Add the IMEM node Kathiravan Thirumoorthy
2025-07-08  6:47   ` Krzysztof Kozlowski [this message]
2025-07-08 10:19     ` Kathiravan Thirumoorthy
2025-07-08 14:19   ` Konrad Dybcio
2025-07-08  5:39 ` [PATCH v2 3/6] arm64: dts: qcom: ipq6018: " Kathiravan Thirumoorthy
2025-07-08 14:19   ` Konrad Dybcio
2025-07-09  4:28     ` Kathiravan Thirumoorthy
2025-07-18 11:45       ` Konrad Dybcio
2025-07-08  5:39 ` [PATCH v2 4/6] arm64: dts: qcom: ipq5018: " Kathiravan Thirumoorthy
2025-07-08 14:20   ` Konrad Dybcio
2025-07-08  5:39 ` [PATCH v2 5/6] arm64: dts: qcom: ipq9574: " Kathiravan Thirumoorthy
2025-07-08 14:21   ` Konrad Dybcio
2025-07-08  5:39 ` [PATCH v2 6/6] arm64: dts: qcom: ipq5332: " Kathiravan Thirumoorthy
2025-07-08 14:21   ` Konrad Dybcio

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=e7ad63b7-523d-4193-97b8-d33601de78f6@kernel.org \
    --to=krzk@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kathiravan.thirumoorthy@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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).