From: Borislav Petkov <bp@alien8.de>
To: Sasha Levin <sashal@kernel.org>
Cc: mchehab@kernel.org, ruizhao@microsoft.com,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kernel@microsoft.com, will.deacon@arm.com,
okaya@kernel.org
Subject: EDAC, dmc520:: add DMC520 EDAC driver
Date: Mon, 21 Jan 2019 13:35:47 +0100 [thread overview]
Message-ID: <20190121123547.GF29166@zn.tnic> (raw)
On Fri, Jan 18, 2019 at 11:23:24AM -0500, Sasha Levin wrote:
> From: Rui Zhao <ruizhao@microsoft.com>
>
> New driver supports DRAM error detection and correction on DMC520
> controller.
That's this thing, right?
https://developer.arm.com/products/system-ip/memory-controllers/corelink-dmc-520
> Validated on actual hardware:
Which is what exactly?
This looks like a driver for the memory controller IP and that could get
integrated in other platforms so I'd prefer if this driver was called
<your_platform>_edac and the DMC520 was a generic piece of functionality
like the FSL memory controller IP:
mpc85xx_edac_mod-y := fsl_ddr_edac.o mpc85xx_edac.o
obj-$(CONFIG_EDAC_MPC85XX) += mpc85xx_edac_mod.o
layerscape_edac_mod-y := fsl_ddr_edac.o layerscape_edac.o
obj-$(CONFIG_EDAC_LAYERSCAPE) += layerscape_edac_mod.o
Thx.
WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@alien8.de>
To: Sasha Levin <sashal@kernel.org>
Cc: mchehab@kernel.org, ruizhao@microsoft.com,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kernel@microsoft.com, will.deacon@arm.com,
okaya@kernel.org
Subject: Re: [PATCH] EDAC, dmc520:: add DMC520 EDAC driver
Date: Mon, 21 Jan 2019 13:35:47 +0100 [thread overview]
Message-ID: <20190121123547.GF29166@zn.tnic> (raw)
In-Reply-To: <20190118162324.17123-1-sashal@kernel.org>
On Fri, Jan 18, 2019 at 11:23:24AM -0500, Sasha Levin wrote:
> From: Rui Zhao <ruizhao@microsoft.com>
>
> New driver supports DRAM error detection and correction on DMC520
> controller.
That's this thing, right?
https://developer.arm.com/products/system-ip/memory-controllers/corelink-dmc-520
> Validated on actual hardware:
Which is what exactly?
This looks like a driver for the memory controller IP and that could get
integrated in other platforms so I'd prefer if this driver was called
<your_platform>_edac and the DMC520 was a generic piece of functionality
like the FSL memory controller IP:
mpc85xx_edac_mod-y := fsl_ddr_edac.o mpc85xx_edac.o
obj-$(CONFIG_EDAC_MPC85XX) += mpc85xx_edac_mod.o
layerscape_edac_mod-y := fsl_ddr_edac.o layerscape_edac.o
obj-$(CONFIG_EDAC_LAYERSCAPE) += layerscape_edac_mod.o
Thx.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next reply other threads:[~2019-01-21 12:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 12:35 Borislav Petkov [this message]
2019-01-21 12:35 ` [PATCH] EDAC, dmc520:: add DMC520 EDAC driver Borislav Petkov
-- strict thread matches above, loose matches on Subject: below --
2019-03-06 5:20 Rui Zhao
2019-03-06 5:20 ` [PATCH] " Rui Zhao
2019-02-05 17:31 James Morse
2019-02-05 17:31 ` [PATCH] " James Morse
2019-02-05 17:31 James Morse
2019-02-05 17:31 ` [PATCH] " James Morse
2019-01-23 22:08 Rui Zhao
2019-01-23 22:08 ` [PATCH] " Rui Zhao
2019-01-23 19:09 Sasha Levin
2019-01-23 19:09 ` [PATCH] " Sasha Levin
2019-01-23 19:03 Borislav Petkov
2019-01-23 19:03 ` [PATCH] " Borislav Petkov
2019-01-23 18:50 Sasha Levin
2019-01-23 18:50 ` [PATCH] " Sasha Levin
2019-01-23 18:46 Borislav Petkov
2019-01-23 18:46 ` [PATCH] " Borislav Petkov
2019-01-23 18:36 James Morse
2019-01-23 18:36 ` [PATCH] " James Morse
2019-01-21 17:09 James Morse
2019-01-21 17:09 ` [PATCH] " James Morse
2019-01-18 16:23 Sasha Levin
2019-01-18 16:23 ` [PATCH] " Sasha Levin
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=20190121123547.GF29166@zn.tnic \
--to=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=okaya@kernel.org \
--cc=ruizhao@microsoft.com \
--cc=sashal@kernel.org \
--cc=will.deacon@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.