From: Krzysztof Kozlowski <krzk@kernel.org>
To: Trilok Soni <trilokkumar.soni@oss.qualcomm.com>
Cc: Umang Chheda <umang.chheda@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>,
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 1/4] dt-bindings: arm: ras: Introduce bindings for ARM RAS error sources
Date: Tue, 28 Jul 2026 10:47:33 +0200 [thread overview]
Message-ID: <20260728-determined-lorikeet-from-tartarus-cf124e@quoll> (raw)
In-Reply-To: <f6443353-b3c5-4922-a98a-1292db381ca7@oss.qualcomm.com>
On Mon, Jul 27, 2026 at 01:51:08PM -0700, Trilok Soni wrote:
> On 7/20/2026 1:19 AM, Umang Chheda wrote:
> > new file mode 100644
> > index 000000000000..c2f4e1f8243e
> > --- /dev/null
> > +++ b/include/dt-bindings/arm/arm-ras.h
> > @@ -0,0 +1,11 @@
> > +/* SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) */
> > +
> > +#ifndef _DT_BINDINGS_ARM_RAS_H
> > +#define _DT_BINDINGS_ARM_RAS_H
> > +
> > +/* arm,group-format - error record group register window page size */
> > +#define ARM_RAS_GROUP_4K 0 /* 4 KiB, 1 ERRGSR */
> > +#define ARM_RAS_GROUP_16K 1 /* 16 KiB, 4 ERRGSRs */
> > +#define ARM_RAS_GROUP_64K 2 /* 64 KiB, 14 ERRGSRs */
>
> Do you want me to have different DT for 4k and 16k and 64k? This is not a right approach.
>
Is this page size or register window page size? If the latter, why would
device registers be a binding?
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-07-28 8:47 UTC|newest]
Thread overview: 15+ 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 [this message]
2026-08-14 11:05 ` Umang Chheda
2026-07-28 8:53 ` Krzysztof Kozlowski
2026-09-03 10:23 ` Umang Chheda
2026-07-31 20:35 ` Rob Herring
2026-08-17 19:58 ` Umang Chheda
2026-10-08 11:42 ` Umang Chheda
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
2026-08-24 9:11 ` Umang Chheda
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=20260728-determined-lorikeet-from-tartarus-cf124e@quoll \
--to=krzk@kernel.org \
--cc=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=trilokkumar.soni@oss.qualcomm.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
all inboxes | Powered by JetHome®