From: Umang Chheda <umang.chheda@oss.qualcomm.com>
To: andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
richardcochran@gmail.com, Borislav Petkov <bp@alien8.de>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Sudeep Holla <sudeep.holla@kernel.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>, Tony Luck <tony.luck@intel.com>,
Robin Murphy <robin.murphy@arm.com>,
Peter Zijlstra <peterz@infradead.org>,
James Morse <james.morse@arm.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-edac@vger.kernel.org,
Ruidong Tian <tianruidong@linux.alibaba.com>,
umang.chheda@oss.qualcomm.com, avaneesh.dwivedi@oss.qualcomm.com,
Faruque Ansari <faruque.ansari@oss.qualcomm.com>
Subject: [PATCH v3 5/5] arm64: dts: qcom: shikra: add RAS error source nodes
Date: Fri, 18 Sep 2026 15:27:46 +0530 [thread overview]
Message-ID: <20260918095746.3347893-6-umang.chheda@oss.qualcomm.com> (raw)
In-Reply-To: <20260918095746.3347893-1-umang.chheda@oss.qualcomm.com>
ARM Reliability, Availability and Serviceability (RAS) enables
processor components (for eg cache, tlb etc) to record and signal
hardware faults through architected error records and fault handling
interrupts. This allows software to detect, report and, where possible,
recover from hardware errors.
The Shikra CPU subsystem implements RAS error records for the L1/L2
cache hierarchy and the shared L3 caches. Describe these error sources
in Device Tree so that the ARM RAS framework can discover them and
handle cache-related error reports.
Co-developed-by: Faruque Ansari <faruque.ansari@oss.qualcomm.com>
Signed-off-by: Faruque Ansari <faruque.ansari@oss.qualcomm.com>
Signed-off-by: Umang Chheda <umang.chheda@oss.qualcomm.com>
---
arch/arm64/boot/dts/qcom/shikra.dtsi | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/shikra.dtsi b/arch/arm64/boot/dts/qcom/shikra.dtsi
index c1f06f692f66..c5bbf1f8e46a 100644
--- a/arch/arm64/boot/dts/qcom/shikra.dtsi
+++ b/arch/arm64/boot/dts/qcom/shikra.dtsi
@@ -330,6 +330,26 @@ opp-2208000000 {
};
};
+ l2-cache-error {
+ compatible = "arm,ras-processor";
+ arm,num-records = <1>;
+ arm,record-impl = /bits/ 64 <0x1>;
+ arm,status-reporting = /bits/ 64 <0x1>;
+ arm,cache-ref = <&l2_3>;
+ interrupts = <GIC_PPI 6 IRQ_TYPE_LEVEL_LOW 0>;
+ interrupt-names = "fhi";
+ };
+
+ l3-cache-error {
+ compatible = "arm,ras-processor";
+ arm,num-records = <2>;
+ arm,record-impl = /bits/ 64 <0x2>;
+ arm,status-reporting = /bits/ 64 <0x2>;
+ arm,cache-ref = <&l3>;
+ interrupts = <GIC_SPI 35 IRQ_TYPE_LEVEL_HIGH 0>;
+ interrupt-names = "fhi";
+ };
+
modem-etm0 {
compatible = "arm,coresight-dummy-source";
--
2.34.1
prev parent reply other threads:[~2026-09-18 9:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 9:57 [PATCH v3 0/5] arm: ras: Add DT frontend support for ARM RAS Umang Chheda
2026-09-18 9:57 ` [PATCH v3 1/5] dt-bindings: arm: ras: Introduce ARM RAS error sources Umang Chheda
2026-09-18 9:57 ` [PATCH v3 2/5] arm64: ras: Add Device Tree frontend Umang Chheda
2026-09-18 9:57 ` [PATCH v3 3/5] arm64: dts: qcom: monaco: add RAS error source nodes Umang Chheda
2026-09-18 9:57 ` [PATCH v3 4/5] arm64: dts: qcom: lemans: " Umang Chheda
2026-09-18 9:57 ` Umang Chheda [this message]
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=20260918095746.3347893-6-umang.chheda@oss.qualcomm.com \
--to=umang.chheda@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=avaneesh.dwivedi@oss.qualcomm.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=faruque.ansari@oss.qualcomm.com \
--cc=james.morse@arm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=richardcochran@gmail.com \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=sudeep.holla@kernel.org \
--cc=tianruidong@linux.alibaba.com \
--cc=tony.luck@intel.com \
--cc=will@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