linux-kernel - Re: [PATCH 4/6] dt-bindings: memory: fsl: Add compatible string nxp,imx9-memory-controller

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <af257b02-5c94-4f3f-a399-40840b594264@kernel.org>
Date: Wed, 10 Jul 2024 08:49:15 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Frank Li <Frank.Li@....com>, York Sun <york.sun@....com>,
 Borislav Petkov <bp@...en8.de>, Tony Luck <tony.luck@...el.com>,
 James Morse <james.morse@....com>, Mauro Carvalho Chehab
 <mchehab@...nel.org>, Robert Richter <rric@...nel.org>,
 Rob Herring <robh@...nel.org>, Conor Dooley <conor+dt@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Shawn Guo <shawnguo@...nel.org>,
 Sascha Hauer <s.hauer@...gutronix.de>,
 Pengutronix Kernel Team <kernel@...gutronix.de>,
 Fabio Estevam <festevam@...il.com>
Cc: linux-edac@...r.kernel.org, linux-kernel@...r.kernel.org,
 Borislav Petkov <bp@...e.de>, devicetree@...r.kernel.org,
 imx@...ts.linux.dev, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 4/6] dt-bindings: memory: fsl: Add compatible string
 nxp,imx9-memory-controller

On 09/07/2024 22:23, Frank Li wrote:
> iMX9 memory controller is similar with other layerscape chips. But some
> register layout has a little bit difference, so add new compatible string
> 'nxp,imx9-memory-controller' for it.
> 
> imx9 need two 'reg', one for DDR controller and the other is ECC inject
> engine register space. Keep the same restriction for other compatible
> string.
> 
> Signed-off-by: Frank Li <Frank.Li@....com>

Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>

I assume this will go via EDAC tree (not memory-controllers tree).

Best regards,
Krzysztof