From: James Morse <james.morse@arm.com>
To: Talel Shenhar <talel@amazon.com>
Cc: robh+dt@kernel.org, mark.rutland@arm.com, bp@alien8.de,
mchehab@kernel.org, davem@davemloft.net,
gregkh@linuxfoundation.org, nicolas.ferre@microchip.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-edac@vger.kernel.org, dwmw@amazon.co.uk,
benh@kernel.crashing.org, hhhawa@amazon.com, ronenk@amazon.com,
jonnyc@amazon.com, hanochu@amazon.com, amirkl@amazon.com,
barakw@amazon.com
Subject: Re: [PATCH v5 2/2] EDAC: al-mc-edac: Introduce Amazon's Annapurna Labs Memory Controller EDAC
Date: Thu, 19 Dec 2019 19:16:58 +0000 [thread overview]
Message-ID: <411bd52f-a714-9b8d-c18c-2d7bcec3d850@arm.com> (raw)
In-Reply-To: <1571911407-29379-3-git-send-email-talel@amazon.com>
Hi Talel,
On 24/10/2019 11:03, Talel Shenhar wrote:
> The Amazon's Annapurna Labs Memory Controller EDAC supports ECC capability
> for error detection and correction (Single bit error correction, Double
> detection). This driver introduces EDAC driver for that capability.
> diff --git a/drivers/edac/al_mc_edac.c b/drivers/edac/al_mc_edac.c
> new file mode 100644
> index 00000000..b9ef7dd
> --- /dev/null
> +++ b/drivers/edac/al_mc_edac.c
> @@ -0,0 +1,355 @@
> +static void devm_al_mc_edac_del(void *data)
> +{
> + edac_mc_del_mc(data);
> +}
> +
> +static void devm_al_mc_edac_free(void *data)
> +{
> + edac_mc_free(data);
> +}
> +
> +static int al_mc_edac_probe(struct platform_device *pdev)
> +{
> + void __iomem *mmio_base;
> + struct edac_mc_layer layers[1];
> + struct mem_ctl_info *mci;
> + struct al_mc_edac *al_mc;
> + int ret;
> +
> + mmio_base = devm_platform_ioremap_resource(pdev, 0);
> + if (IS_ERR(mmio_base)) {
> + dev_err(&pdev->dev, "failed to ioremap memory (%ld)\n",
> + PTR_ERR(mmio_base));
> + return PTR_ERR(mmio_base);
> + }
> +
> + layers[0].type = EDAC_MC_LAYER_CHIP_SELECT;
> + layers[0].size = 1;
> + layers[0].is_virt_csrow = false;
> + mci = edac_mc_alloc(0, ARRAY_SIZE(layers), layers,
> + sizeof(struct al_mc_edac));
> + if (!mci)
> + return -ENOMEM;
> + ret = devm_add_action(&pdev->dev, devm_al_mc_edac_free, mci);
> + if (ret) {
> + edac_mc_free(mci);
> + return ret;
> + }
Cool. (edac_mc.c should probably provide a devm_edac_mc_alloc() that does this, but that
can be future)
> +static struct platform_driver al_mc_edac_driver = {
> + .probe = al_mc_edac_probe,
(Looks like you can still remove the module even though there is no .remove here.)
Reviewed-by: James Morse <james.morse@arm.com>
Thanks,
James
prev parent reply other threads:[~2019-12-19 19:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 10:03 [PATCH v5 0/2] Amazon's Annapurna Labs Memory Controller EDAC Talel Shenhar
2019-10-24 10:03 ` [PATCH v5 1/2] dt-bindings: edac: al-mc-edac: " Talel Shenhar
2019-10-24 22:46 ` Rob Herring
2019-10-24 10:03 ` [PATCH v5 2/2] EDAC: al-mc-edac: Introduce " Talel Shenhar
2019-12-19 19:16 ` James Morse [this message]
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=411bd52f-a714-9b8d-c18c-2d7bcec3d850@arm.com \
--to=james.morse@arm.com \
--cc=amirkl@amazon.com \
--cc=barakw@amazon.com \
--cc=benh@kernel.crashing.org \
--cc=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dwmw@amazon.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=hanochu@amazon.com \
--cc=hhhawa@amazon.com \
--cc=jonnyc@amazon.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=robh+dt@kernel.org \
--cc=ronenk@amazon.com \
--cc=talel@amazon.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).