From: Yash Shah <yash.shah@sifive.com>
To: linux-riscv@lists.infradead.org, linux-edac@vger.kernel.org,
palmer@sifive.com, paul.walmsley@sifive.com
Cc: linux-kernel@vger.kernel.org, robh+dt@kernel.org,
mark.rutland@arm.com, aou@eecs.berkeley.edu, bp@alien8.de,
mchehab@kernel.org, devicetree@vger.kernel.org,
sachin.ghadi@sifive.com, Yash Shah <yash.shah@sifive.com>
Subject: [PATCH 0/2] EDAC Support for SiFive SoCs
Date: Wed, 20 Mar 2019 17:22:06 +0530 [thread overview]
Message-ID: <1553082728-9232-1-git-send-email-yash.shah@sifive.com> (raw)
This patch series adds an EDAC driver and DT documentation
for FU540-C000 chip.
Initially L2 Cache controller is added as a subcomponent to this driver.
This patchset is based on Linux 5.0-rc8 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 (2):
edac: sifive: Add DT documentation for SiFive EDAC driver and
subcomponent
edac: sifive: Add EDAC driver for SiFive FU540-C000 chip
.../devicetree/bindings/edac/sifive-edac.txt | 40 +++
arch/riscv/Kconfig | 1 +
drivers/edac/Kconfig | 13 +
drivers/edac/Makefile | 1 +
drivers/edac/sifive_edac.c | 297 +++++++++++++++++++++
5 files changed, 352 insertions(+)
create mode 100644 Documentation/devicetree/bindings/edac/sifive-edac.txt
create mode 100644 drivers/edac/sifive_edac.c
--
1.9.1
next reply other threads:[~2019-03-20 11:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 11:52 Yash Shah [this message]
2019-03-20 11:52 ` [PATCH 1/2] edac: sifive: Add DT documentation for SiFive EDAC driver and subcomponent Yash Shah
2019-03-25 0:20 ` Paul Walmsley
2019-03-20 11:52 ` [PATCH 2/2] edac: sifive: Add EDAC driver for SiFive FU540-C000 chip Yash Shah
2019-03-21 13:33 ` Borislav Petkov
2019-03-22 6:00 ` Yash Shah
2019-03-25 0:23 ` Paul Walmsley
2019-03-25 6:57 ` Borislav Petkov
2019-03-25 21:26 ` Paul Walmsley
2019-03-25 21:50 ` Borislav Petkov
2019-03-29 19:45 ` Paul Walmsley
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=1553082728-9232-1-git-send-email-yash.shah@sifive.com \
--to=yash.shah@sifive.com \
--cc=aou@eecs.berkeley.edu \
--cc=bp@alien8.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--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).