linux-kernel - Re: [PATCH 3/3] ARM: dts: mxs: support i.MX28 Amarula rmm board

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: <CAOMZO5DBL0BD_YbByqTHRGq_FkxG9vD_ycXiPTJdQ4WfmKfitA@mail.gmail.com>
Date: Fri, 23 May 2025 10:05:00 -0300
From: Fabio Estevam <festevam@...il.com>
To: Dario Binacchi <dario.binacchi@...rulasolutions.com>
Cc: linux-kernel@...r.kernel.org, linux-amarula@...rulasolutions.com, 
	michael@...rulasolutions.com, Conor Dooley <conor+dt@...nel.org>, 
	Krzysztof Kozlowski <krzk+dt@...nel.org>, Pengutronix Kernel Team <kernel@...gutronix.de>, 
	Rob Herring <robh@...nel.org>, Sascha Hauer <s.hauer@...gutronix.de>, 
	Shawn Guo <shawnguo@...nel.org>, devicetree@...r.kernel.org, imx@...ts.linux.dev, 
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 3/3] ARM: dts: mxs: support i.MX28 Amarula rmm board

Hi Dario,

On Wed, May 21, 2025 at 10:20 AM Dario Binacchi
<dario.binacchi@...rulasolutions.com> wrote:

> So if you're okay with it, I will remove all references to the LCD
> display — both from the commit
> message and from the DTS, such as the reset pin, for example.

Yes, that's OK.

> We have two models, one with 128MB and one with 256MB of RAM.
> What's the recommended way to handle both cases?
> Should I define a new DTS file named imx28-amarula-rmm-256mb.dts
> that includes imx28-amarula-rmm.dts and override the reg property of
> the memory node?

Or maybe you can describe 128MB in the dts and let the bootloader run
a fixup on the memory size, adjusting it if needed?