From: Vijay Balakrishna <vijayb@linux.microsoft.com>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: Borislav Petkov <bp@alien8.de>, Tony Luck <tony.luck@intel.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
James Morse <james.morse@arm.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Robert Richter <rric@kernel.org>,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
Tyler Hicks <code@tyhicks.com>, Marc Zyngier <maz@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/3] drivers/edac: Add L1 and L2 error detection for A72
Date: Fri, 23 May 2025 11:26:48 -0700 [thread overview]
Message-ID: <a40e3c38-4ccc-45c8-921d-2d8ed8fe449b@linux.microsoft.com> (raw)
In-Reply-To: <20250520103500.00003905@huawei.com>
On 5/20/25 02:35, Jonathan Cameron wrote:
> On Thu, 15 May 2025 17:06:11 -0700
> Vijay Balakrishna<vijayb@linux.microsoft.com> wrote:
>
>> From: Sascha Hauer<s.hauer@pengutronix.de>
>>
>> The Cortex A72 cores have error detection capabilities for
>> the L1/L2 Caches, this patch adds a driver for them. The selected errors
>> to detect/report are by reading CPU/L2 memory error syndrome registers.
>>
>> Unfortunately there is no robust way to inject errors into the caches,
>> so this driver doesn't contain any code to actually test it. It has
>> been tested though with code taken from an older version [1] of this
>> driver. For reasons stated in thread [1], the error injection code is
>> not suitable for mainline, so it is removed from the driver.
>>
>> [1]https://lore.kernel.org/all/1521073067-24348-1-git-send-email-york.sun@nxp.com/#t
>>
>> Signed-off-by: Sascha Hauer<s.hauer@pengutronix.de>
>> Co-developed-by: Vijay Balakrishna<vijayb@linux.microsoft.com>
>> Signed-off-by: Vijay Balakrishna<vijayb@linux.microsoft.com>
> Hi.
>
> Some issues with release of device_nodes in the of parsing code.
Thank you, Jonathan for review. I'm addressing your comments and posting
next series soon.
Vijay
next prev parent reply other threads:[~2025-05-23 18:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 0:06 [v9 PATCH 0/3] Add L1 and L2 error detection for A72 Vijay Balakrishna
2025-05-16 0:06 ` [PATCH 1/3] drivers/edac: " Vijay Balakrishna
2025-05-19 8:51 ` Borislav Petkov
2025-05-20 16:09 ` Vijay Balakrishna
2025-05-20 19:54 ` Vijay Balakrishna
2025-05-20 20:04 ` Borislav Petkov
2025-05-20 23:20 ` Vijay Balakrishna
2025-05-20 9:35 ` Jonathan Cameron
2025-05-23 18:26 ` Vijay Balakrishna [this message]
2025-05-16 0:06 ` [PATCH 2/3] dt-bindings: arm: cpus: Add edac-enabled property Vijay Balakrishna
2025-05-19 9:02 ` Borislav Petkov
2025-05-21 0:07 ` Rob Herring
2025-05-21 5:56 ` Vijay Balakrishna
2025-05-16 0:06 ` [PATCH 3/3] EDAC: Add EDAC driver for Cortex A72 Vijay Balakrishna
2025-05-19 9:04 ` Borislav Petkov
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=a40e3c38-4ccc-45c8-921d-2d8ed8fe449b@linux.microsoft.com \
--to=vijayb@linux.microsoft.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=bp@alien8.de \
--cc=code@tyhicks.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=james.morse@arm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=maz@kernel.org \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
--cc=rric@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=tony.luck@intel.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;
as well as URLs for NNTP newsgroup(s).