[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190325220129.GV12016@zn.tnic>
Date: Mon, 25 Mar 2019 23:01:29 +0100
From: Borislav Petkov <bp@...en8.de>
To: James Morse <james.morse@....com>
Cc: Rui Zhao <ruizhao@...look.com>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"mark.rutland@....com" <mark.rutland@....com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
"okaya@...nel.org" <okaya@...nel.org>,
"mchehab@...nel.org" <mchehab@...nel.org>,
"will.deacon@....com" <will.deacon@....com>,
"sashal@...nel.org" <sashal@...nel.org>,
"hangl@...rosoft.com" <hangl@...rosoft.com>,
"lewan@...rosoft.com" <lewan@...rosoft.com>,
Rui Zhao <ruizhao@...rosoft.com>
Subject: Re: [PATCH v2 1/2] EDAC: add EDAC driver for DMC520
On Mon, Mar 25, 2019 at 06:27:52PM +0000, James Morse wrote:
> or even:
> | compatible = "microsoft,product-name-dmc520", "arm,dmc-520";
> if there is some firmware/board configuration that means vendor/soc isn't precise enough.
Yap, makes sense to me. If dmc-520 is a memory controller IP, then it
should be a generic, library-like compilation unit which the platform
driver, i.e., <microsoft-platform-name>_edac.c or so links with.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
Powered by blists - more mailing lists