From: Kathiravan Thirumoorthy <kathiravan.thirumoorthy@oss.qualcomm.com>
To: 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: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
Kathiravan Thirumoorthy
<kathiravan.thirumoorthy@oss.qualcomm.com>
Subject: [PATCH v3 2/6] arm64: dts: qcom: ipq8074: Add the IMEM node
Date: Sat, 28 Feb 2026 18:38:01 +0530 [thread overview]
Message-ID: <20260228-imem-v3-2-20fbcc1a9404@oss.qualcomm.com> (raw)
In-Reply-To: <20260228-imem-v3-0-20fbcc1a9404@oss.qualcomm.com>
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>
---
arch/arm64/boot/dts/qcom/ipq8074.dtsi | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/ipq8074.dtsi b/arch/arm64/boot/dts/qcom/ipq8074.dtsi
index 256e12cf6d54417582a8b50e061f40719a4004a1..086b34ba7b09d68e24d2c1da28f303357ce503ea 100644
--- a/arch/arm64/boot/dts/qcom/ipq8074.dtsi
+++ b/arch/arm64/boot/dts/qcom/ipq8074.dtsi
@@ -625,6 +625,17 @@ qpic_nand: nand-controller@79b0000 {
status = "disabled";
};
+ sram@8600000 {
+ compatible = "qcom,ipq8074-imem", "mmio-sram";
+ reg = <0x08600000 0x6000>;
+ ranges = <0 0x08600000 0x6000>;
+
+ no-memory-wc;
+
+ #address-cells = <1>;
+ #size-cells = <1>;
+ };
+
usb_0: usb@8af8800 {
compatible = "qcom,ipq8074-dwc3", "qcom,dwc3";
reg = <0x08af8800 0x400>;
--
2.34.1
next prev parent reply other threads:[~2026-02-28 13:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-28 13:07 [PATCH v3 0/6] Describe the IMEM present in Qualcomm IPQ SoC's Kathiravan Thirumoorthy
2026-02-28 13:08 ` [PATCH v3 1/6] dt-bindings: sram: Describe the IMEM present in Qualcomm IPQ SoCs Kathiravan Thirumoorthy
2026-03-01 11:27 ` Krzysztof Kozlowski
2026-03-02 13:52 ` Konrad Dybcio
2026-03-02 13:56 ` Krzysztof Kozlowski
2026-03-02 14:10 ` Konrad Dybcio
2026-03-02 14:54 ` Krzysztof Kozlowski
2026-03-02 14:56 ` Konrad Dybcio
2026-03-02 16:33 ` Krzysztof Kozlowski
2026-03-03 10:48 ` Konrad Dybcio
2026-03-04 11:16 ` Kathiravan Thirumoorthy
2026-03-04 11:29 ` Krzysztof Kozlowski
2026-03-04 11:38 ` Konrad Dybcio
2026-03-04 11:44 ` Krzysztof Kozlowski
2026-02-28 13:08 ` Kathiravan Thirumoorthy [this message]
2026-03-01 11:29 ` [PATCH v3 2/6] arm64: dts: qcom: ipq8074: Add the IMEM node Krzysztof Kozlowski
2026-02-28 13:08 ` [PATCH v3 3/6] arm64: dts: qcom: ipq6018: " Kathiravan Thirumoorthy
2026-02-28 13:08 ` [PATCH v3 4/6] arm64: dts: qcom: ipq5018: " Kathiravan Thirumoorthy
2026-02-28 13:08 ` [PATCH v3 5/6] arm64: dts: qcom: ipq9574: " Kathiravan Thirumoorthy
2026-02-28 13:08 ` [PATCH v3 6/6] arm64: dts: qcom: ipq5332: " Kathiravan Thirumoorthy
2026-03-01 11:28 ` Krzysztof Kozlowski
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=20260228-imem-v3-2-20fbcc1a9404@oss.qualcomm.com \
--to=kathiravan.thirumoorthy@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=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