[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHpyw9dn=3sGfjcqtQN-GwdoCo=dfhOrofTGMZJc+2Jjpr7pAw@mail.gmail.com>
Date: Mon, 14 Mar 2022 16:24:30 +0800
From: Medad Young <medadyoung@...il.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>
Cc: rric@...nel.org, James Morse <james.morse@....com>,
tony.luck@...el.com, Mauro Carvalho Chehab <mchehab@...nel.org>,
Borislav Petkov <bp@...en8.de>,
Rob Herring <robh+dt@...nel.org>,
Benjamin Fair <benjaminfair@...gle.com>,
Nancy Yuen <yuenn@...gle.com>,
Patrick Venture <venture@...gle.com>, KWLIU@...oton.com,
YSCHU@...oton.com, JJLIU0@...oton.com, KFTING <KFTING@...oton.com>,
Avi Fishman <avifishman70@...il.com>,
Tomer Maimon <tmaimon77@...il.com>,
Tali Perry <tali.perry1@...il.com>, ctcchien@...oton.com,
linux-edac <linux-edac@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
devicetree <devicetree@...r.kernel.org>,
OpenBMC Maillist <openbmc@...ts.ozlabs.org>
Subject: Re: [PATCH v3 3/3] EDAC: nuvoton: Add NPCM memory controller driver
Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com> 於 2022年3月14日
週一 下午3:36寫道:
>
> On 14/03/2022 06:32, Medad Young wrote:
> > Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com> 於 2022年3月11日
> > 週五 下午5:15寫道:
> >>
> >> On 11/03/2022 02:42, Medad CChien wrote:
> >>> Add support for Nuvoton NPCM SoC.
> >>>
> >>> Signed-off-by: Medad CChien <ctcchien@...oton.com>
> >>> ---
> >>> drivers/edac/Kconfig | 9 +
> >>> drivers/edac/Makefile | 1 +
> >>> drivers/edac/npcm_edac.c | 714 +++++++++++++++++++++++++++++++++++++++
> >>> 3 files changed, 724 insertions(+)
> >>> create mode 100644 drivers/edac/npcm_edac.c
> >>>
> >>> diff --git a/drivers/edac/Kconfig b/drivers/edac/Kconfig
> >>> index 58ab63642e72..757e1d160640 100644
> >>> --- a/drivers/edac/Kconfig
> >>> +++ b/drivers/edac/Kconfig
> >>> @@ -539,4 +539,13 @@ config EDAC_DMC520
> >>> Support for error detection and correction on the
> >>> SoCs with ARM DMC-520 DRAM controller.
> >>>
> >>> +config EDAC_NPCM
> >>> + tristate "Nuvoton NPCM DDR Memory Controller"
> >>> + depends on ARCH_NPCM
> >>
> >> || COMPILE_TEST
> >> (and test if it compiles)
> >>
> >> (...)
> >>
> >>> +
> >>> +MODULE_DEVICE_TABLE(of, npcm_edac_of_match);
> >>> +
> >>> +static int npcm_edac_mc_probe(struct platform_device *pdev)
> >>> +{
> >>> + const struct npcm_edac_platform_data *npcm_chip;
> >>> + struct device *dev = &pdev->dev;
> >>> + struct edac_mc_layer layers[1];
> >>> + const struct of_device_id *id;
> >>> + struct priv_data *priv_data;
> >>> + struct mem_ctl_info *mci;
> >>> + struct resource *res;
> >>> + void __iomem *reg;
> >>> + int ret = -ENODEV;
> >>> + int irq;
> >>> +
> >>> + id = of_match_device(npcm_edac_of_match, &pdev->dev);
> >>> + if (!id)
> >>> + return -ENODEV;
> >>
> >> Why do you need it? How such case is even possible?
> > this driver is used for two nuvoton SOCs, one is NPCM845 and the other
> > is NPCM750
>
> Yes and how NULL can happen for OF-only driver? Unless I missed
> something and this is not an OF-only driver? Do you allow any other
> matching methods?
I got your point, thanks
> Best regards,
> Krzysztof
Powered by blists - more mailing lists