From: Bjorn Andersson <andersson@kernel.org>
To: Umang Chheda <umang.chheda@oss.qualcomm.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Ruidong Tian <tianruidong@linux.alibaba.com>,
Tony Luck <tony.luck@intel.com>, Borislav Petkov <bp@alien8.de>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-edac@vger.kernel.org, faruque.ansari@oss.qualcomm.com,
avaneesh.dwivedi@oss.qualcomm.com
Subject: Re: [PATCH v2 3/4] arm64: dts: qcom: monaco: add RAS error source nodes
Date: Sat, 1 Aug 2026 22:49:30 -0500 [thread overview]
Message-ID: <am69fjQNTv2xJonT@baldur> (raw)
In-Reply-To: <20260720081954.1858180-4-umang.chheda@oss.qualcomm.com>
On Mon, Jul 20, 2026 at 01:49:53PM +0530, Umang Chheda wrote:
> Add RAS error source nodes for the Monaco SoC.
Why is the subject "repeated" here?
>
> Two processor error sources are described: a per-PE node covering the
> L1/L2 cache hierarchy using a PPI, and two shared L3 cache nodes for
> the two CPU clusters using SPIs.
Please read
https://docs.kernel.org/process/submitting-patches.html#describe-your-changes
and don't assume the reader know what this is and why it might be
useful.
>
> 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/monaco.dtsi | 30 ++++++++++++++++++++++++++++
> 1 file changed, 30 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/qcom/monaco.dtsi b/arch/arm64/boot/dts/qcom/monaco.dtsi
> index 64fc0d592282..4fbd1dc9a147 100644
> --- a/arch/arm64/boot/dts/qcom/monaco.dtsi
> +++ b/arch/arm64/boot/dts/qcom/monaco.dtsi
> @@ -724,6 +724,36 @@ system_pd: power-domain-system {
> };
> };
>
> + ras-l1l2-0 {
Why is there a -0 suffix on this node?
Regards,
Bjorn
> + compatible = "arm,ras-processor";
> + arm,num-records = <1>;
> + arm,record-impl = /bits/ 64 <0x1>;
> + arm,status-reporting = /bits/ 64 <0x1>;
> + cache = <&l2_0>;
> + interrupts = <GIC_PPI 0 IRQ_TYPE_LEVEL_LOW>;
> + interrupt-names = "fhi";
> + };
> +
> + ras-l3-cluster0 {
> + compatible = "arm,ras-processor";
> + arm,num-records = <2>;
> + arm,record-impl = /bits/ 64 <0x2>;
> + arm,status-reporting = /bits/ 64 <0x2>;
> + cache = <&l3_0>;
> + interrupts = <GIC_SPI 36 IRQ_TYPE_LEVEL_HIGH>;
> + interrupt-names = "fhi";
> + };
> +
> + ras-l3-cluster1 {
> + compatible = "arm,ras-processor";
> + arm,num-records = <2>;
> + arm,record-impl = /bits/ 64 <0x2>;
> + arm,status-reporting = /bits/ 64 <0x2>;
> + cache = <&l3_1>;
> + interrupts = <GIC_SPI 21 IRQ_TYPE_LEVEL_HIGH>;
> + interrupt-names = "fhi";
> + };
> +
> reserved-memory {
> #address-cells = <2>;
> #size-cells = <2>;
> --
> 2.34.1
>
next prev parent reply other threads:[~2026-08-02 3:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 8:19 [PATCH v2 0/4] arm: ras: Add DT frontend support for ARM RAS Umang Chheda
2026-07-20 8:19 ` [PATCH v2 1/4] dt-bindings: arm: ras: Introduce bindings for ARM RAS error sources Umang Chheda
2026-07-27 20:51 ` Trilok Soni
2026-07-28 8:47 ` Krzysztof Kozlowski
2026-07-28 8:53 ` Krzysztof Kozlowski
2026-07-31 20:35 ` Rob Herring
2026-07-20 8:19 ` [PATCH v2 2/4] arm64: ras: Add Device Tree frontend Umang Chheda
2026-07-20 8:19 ` [PATCH v2 3/4] arm64: dts: qcom: monaco: add RAS error source nodes Umang Chheda
2026-08-02 3:49 ` Bjorn Andersson [this message]
2026-07-20 8:19 ` [PATCH v2 4/4] arm64: dts: qcom: lemans: " Umang Chheda
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=am69fjQNTv2xJonT@baldur \
--to=andersson@kernel.org \
--cc=avaneesh.dwivedi@oss.qualcomm.com \
--cc=bp@alien8.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=faruque.ansari@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tianruidong@linux.alibaba.com \
--cc=tony.luck@intel.com \
--cc=umang.chheda@oss.qualcomm.com \
/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