From: Yash Shah <yash.shah@sifive.com>
To: linux-edac@vger.kernel.org, linux-riscv@lists.infradead.org,
palmer@sifive.com, bp@alien8.de, james.morse@arm.com
Cc: paul.walmsley@sifive.com, linux-kernel@vger.kernel.org,
aou@eecs.berkeley.edu, mchehab@kernel.org,
sachin.ghadi@sifive.com, davem@davemloft.net,
gregkh@linuxfoundation.org, nicolas.ferre@microchip.com,
paulmck@linux.ibm.com, Yash Shah <yash.shah@sifive.com>
Subject: [PATCH] EDAC support for SiFive SoCs
Date: Thu, 2 May 2019 16:46:00 +0530 [thread overview]
Message-ID: <1556795761-21630-1-git-send-email-yash.shah@sifive.com> (raw)
Adds an EDAC platform driver for SiFive SoCs.
This patch was earlier part of the patch series:
'L2 cache controller and EDAC support for SiFive SoCs'
https://lkml.org/lkml/2019/4/15/320
In order to merge L2 cache controller driver without any dependency on EDAC,
this EDAC patch is re-posted separately with updated MAINTAINERS entry.
This patch depends on patch
'RISC-V: sifive_l2_cache: Add L2 cache controller driver for SiFive SoCs'
https://lkml.org/lkml/2019/5/2/309
The EDAC driver registers for notifier events from the L2 cache controller
driver (arch/riscv/mm/sifive_l2_cache.c) for L2 ECC events
The patch is based on Linux 5.1-rc2 and tested on HiFive Unleashed board
with additional board related patches needed for testing can be found at
dev/yashs/L2_cache_controller branch of:
https://github.com/yashshah7/riscv-linux.git
Yash Shah (1):
edac: sifive: Add EDAC platform driver for SiFive SoCs
MAINTAINERS | 6 +++
arch/riscv/Kconfig | 1 +
drivers/edac/Kconfig | 6 +++
drivers/edac/Makefile | 1 +
drivers/edac/sifive_edac.c | 121 +++++++++++++++++++++++++++++++++++++++++++++
5 files changed, 135 insertions(+)
create mode 100644 drivers/edac/sifive_edac.c
--
1.9.1
next reply other threads:[~2019-05-02 11:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 11:16 Yash Shah [this message]
2019-05-02 11:16 ` [PATCH] edac: sifive: Add EDAC platform driver for SiFive SoCs Yash Shah
2019-05-02 16:42 ` James Morse
2019-05-03 19:25 ` Paul Walmsley
2019-05-06 9:50 ` Yash Shah
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=1556795761-21630-1-git-send-email-yash.shah@sifive.com \
--to=yash.shah@sifive.com \
--cc=aou@eecs.berkeley.edu \
--cc=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=paulmck@linux.ibm.com \
--cc=sachin.ghadi@sifive.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).