On 7/2/25 12:17 PM, Kathiravan Thirumoorthy wrote:Thanks, I cross checked this in the SoC and I'm able to access the full 4 byte at the end. Let me fix this up in the V2.
Add the IMEM node to the device tree to extract debugging informationI firmly believe there's an off-by-one in the docs and there
like system restart reason, which is populated via IMEM. Define the
IMEM region to enable this functionality.
As described, overall IMEM region is approximately 32KB but only initial
4KB is accessible by all masters in the SoC.
Signed-off-by: Kathiravan Thirumoorthy <kathiravan.thirumoorthy@xxxxxxxxxxxxxxxx>
---
arch/arm64/boot/dts/qcom/ipq6018.dtsi | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/ipq6018.dtsi b/arch/arm64/boot/dts/qcom/ipq6018.dtsi
index bfe59b0208415902c69fd0c0c7565d97997d4207..7eca5ba416c2ef5ef1c4e0eb4f58f1ca94fc92f0 100644
--- a/arch/arm64/boot/dts/qcom/ipq6018.dtsi
+++ b/arch/arm64/boot/dts/qcom/ipq6018.dtsi
@@ -659,6 +659,15 @@ qpic_nand: nand-controller@79b0000 {
status = "disabled";
};
+ sram@8600000 {
+ compatible = "qcom,ipq6018-imem", "syscon", "simple-mfd";
+ reg = <0 0x08600000 0 0x7fff>;
+ ranges = <0 0 0x08600000 0x7fff>;
isn't an odd number of bytes reserved in the hw
Konrad