From: Stefan Schaeckeler <schaecsn@gmx.net>
To: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Joel Stanley <joel@jms.id.au>, Andrew Jeffery <andrew@aj.id.au>,
Borislav Petkov <bp@alien8.de>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-edac@vger.kernel.org
Cc: Stefan M Schaeckeler <schaecsn@gmx.net>
Subject: [PATCH 0/2] Add support for the Aspeed AST2500 SoC EDAC driver.
Date: Sun, 16 Dec 2018 22:01:55 -0800 [thread overview]
Message-ID: <1545026517-64069-1-git-send-email-schaecsn@gmx.net> (raw)
From: Stefan M Schaeckeler <schaecsn@gmx.net>
Add support for the Aspeed AST2500 SoC EDAC driver.
Note, I only have access to AST2500 hardware and documentation. The AST2500
documentation explicitly states that the sdram controller is not backward
compatible with AST2400 and hence this driver is not supporting it.
Best, Stefan
Stefan M Schaeckeler (2):
EDAC: Add Aspeed AST2500 EDAC driver
dt-bindings: edac: Aspeed AST2500
.../bindings/edac/aspeed-sdram-edac.txt | 34 ++
MAINTAINERS | 6 +
arch/arm/boot/dts/aspeed-g5.dtsi | 7 +
drivers/edac/Kconfig | 7 +
drivers/edac/Makefile | 1 +
drivers/edac/aspeed_edac.c | 457 ++++++++++++++++++
6 files changed, 512 insertions(+)
create mode 100644 Documentation/devicetree/bindings/edac/aspeed-sdram-edac.txt
create mode 100644 drivers/edac/aspeed_edac.c
--
2.19.1
next reply other threads:[~2018-12-17 6:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 6:01 Stefan Schaeckeler [this message]
2018-12-17 6:01 ` [PATCH 1/2] EDAC: Add Aspeed AST2500 EDAC driver Stefan Schaeckeler
2018-12-31 13:20 ` Stefan Schaeckeler
2018-12-31 13:53 ` Boris Petkov
2019-01-10 9:50 ` Borislav Petkov
2019-01-15 17:57 ` Stefan Schaeckeler
2019-01-16 21:30 ` Borislav Petkov
2018-12-17 6:01 ` [PATCH 2/2] dt-bindings: edac: Aspeed AST2500 Stefan Schaeckeler
2018-12-27 22:09 ` Rob Herring
2018-12-29 18:30 ` schaecsn
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=1545026517-64069-1-git-send-email-schaecsn@gmx.net \
--to=schaecsn@gmx.net \
--cc=andrew@aj.id.au \
--cc=bp@alien8.de \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.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).