From: rvaswani@codeaurora.org (Rohit Vaswani)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] arm64: enable EDAC on arm64
Date: Mon, 14 Apr 2014 15:21:29 -0700 [thread overview]
Message-ID: <534C5F69.8030208@codeaurora.org> (raw)
In-Reply-To: <loom.20140410T150903-818@post.gmane.org>
On 4/10/2014 6:10 AM, Tomasz Nowicki wrote:
> Rob Herring <robherring2 <at> gmail.com> writes:
>
>> From: Rob Herring <rob.herring <at> calxeda.com>
>>
>> Implement atomic_scrub and enable EDAC for arm64.
>>
>> Signed-off-by: Rob Herring <rob.herring <at> calxeda.com>
>> Cc: Catalin Marinas <catalin.marinas <at> arm.com>
>> Cc: Will Deacon <will.deacon <at> arm.com>
>> ---
>> v2:
>> - Add loop for exclusive store success
>> - Fix size to be 32-bits at a time. The framework gives no alignment
>> guarantees.
>>
> Hi Rob,
>
> I am working on memory error for ARM64 and wondering what is your plans
> regarding this patch. It looks essential for my further work.
>
> Regards,
> Tomasz
>
Hi Tomasz, Rob,
I am looking at similar information for A53 and A57 for the L1/L2 single
and double bit ecc errors.
Is there an upstream/linaro effort for EDAC driver in progress ?
-Rohit
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Thanks,
Rohit Vaswani
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation
next prev parent reply other threads:[~2014-04-14 22:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 21:05 [PATCH v2] arm64: enable EDAC on arm64 Rob Herring
2013-11-25 18:20 ` Will Deacon
2013-11-26 15:24 ` Rob Herring
2013-11-26 15:37 ` Catalin Marinas
2013-12-05 0:53 ` Rob Herring
2013-12-05 11:51 ` Catalin Marinas
2013-12-05 13:52 ` Rob Herring
2013-12-05 15:34 ` Catalin Marinas
2014-04-10 13:10 ` Tomasz Nowicki
2014-04-14 22:21 ` Rohit Vaswani [this message]
2014-04-21 16:19 ` Rob Herring
2014-04-22 13:01 ` Tomasz Nowicki
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=534C5F69.8030208@codeaurora.org \
--to=rvaswani@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).