From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Fri, 23 Apr 2021 12:24:19 -0400 Subject: [PATCH v2 7/8] lmb: Add 2 config to define the max number of regions In-Reply-To: <20210310101622.v2.7.Icdf0b7e662fc65658e591ce0f692a5695f607256@changeid> References: <20210310091632.17103-1-patrick.delaunay@foss.st.com> <20210310101622.v2.7.Icdf0b7e662fc65658e591ce0f692a5695f607256@changeid> Message-ID: <20210423162419.GT1310@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Wed, Mar 10, 2021 at 10:16:31AM +0100, Patrick Delaunay wrote: > Add 2 configs CONFIG_LMB_MEMORY_REGIONS and CONFIG_LMB_RESERVED_REGIONS > to change independently the max number of the regions in lmb > library. > > When CONFIG_LMB_USE_MAX_REGIONS=y, move the lmb property arrays to > struct lmb and manage the array size with the element 'max' of struct > lmb_region; their are still allocated in stack. > > When CONFIG_LMB_USE_MAX_REGIONS=n, keep the current location in > struct lmb_region to allow compiler optimization. > > Increase CONFIG_LMB_RESERVED_REGIONS is useful to avoid lmb errors in > bootm when the number of reserved regions (not adjacent) is reached: > + 1 region for relocated U-Boot > + 1 region for initrd > + 1 region for relocated linux device tree > + reserved memory regions present in Linux device tree. > > The current limit of 8 regions is reached with only 5 reserved regions > in DT. > > see Linux kernel commit bf23c51f1f49 ("memblock: Move memblock arrays > to static storage in memblock.c and make their size a variable") > > Signed-off-by: Patrick Delaunay Applied to u-boot/master, thanks! -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 659 bytes Desc: not available URL: