From: thor.thayer@linux.intel.com
To: bp@alien8.de, dinguyen@kernel.org, linux@armlinux.org.uk,
mchehab@kernel.org, james.morse@arm.com
Cc: thor.thayer@linux.intel.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-edac@vger.kernel.org
Subject: [PATCHv2 0/2] Independent SOCFPGA SDRAM EDAC config
Date: Mon, 25 Feb 2019 12:56:44 -0600 [thread overview]
Message-ID: <1551121006-4657-1-git-send-email-thor.thayer@linux.intel.com> (raw)
From: Thor Thayer <thor.thayer@linux.intel.com>
Most users want EDAC support so make it the default.
SOCFPGA SDRAM EDAC reporting was enabled by the parent EDAC
config (CONFIG_ALTERA_EDAC) since initial customers always
wanted SDRAM EDAC enabled.
There are cases where the SDRAM needs to be disabled while
the other block EDACs remain enabled.
This patch set 1) splits out the SDRAM EDAC into a separate
config and 2) enables all the EDAC blocks by default for
32 bit SOCFPGA.
V2 Changes
Rebase socfpga_defconfig against arm-soc/arm/defconfig
Thor Thayer (2):
EDAC, altera: Add separate SDRAM EDAC config
ARM: socfpga_defconfig: enable EDAC by default
arch/arm/configs/socfpga_defconfig | 12 +++++++
drivers/edac/Kconfig | 14 ++++++--
drivers/edac/altera_edac.c | 67 ++++++++++++++++++++------------------
3 files changed, 59 insertions(+), 34 deletions(-)
--
2.7.4
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-02-25 19:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 18:56 thor.thayer [this message]
2019-02-25 18:56 ` [PATCHv2 1/2] EDAC, altera: Add separate SDRAM EDAC config thor.thayer
2019-02-25 18:56 ` [PATCHv2 2/2] ARM: socfpga_defconfig: enable EDAC by default thor.thayer
2019-02-25 20:42 ` [PATCHv2 0/2] Independent SOCFPGA SDRAM EDAC config Borislav Petkov
2019-02-26 14:59 ` Dinh Nguyen
2019-02-26 17:47 ` 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=1551121006-4657-1-git-send-email-thor.thayer@linux.intel.com \
--to=thor.thayer@linux.intel.com \
--cc=bp@alien8.de \
--cc=dinguyen@kernel.org \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mchehab@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).