From: Fabio Estevam <festevam@gmail.com>
To: sbabic@denx.de
Cc: u-boot@lists.denx.de, heiko.thiery@gmail.com, xypron.glpk@gmx.de,
trini@konsulko.com, aford173@gmail.com,
marcel.ziswiler@toradex.com, mingkai.hu@nxp.com,
priyanka.jain@nxp.com, Fabio Estevam <festevam@denx.de>
Subject: [PATCH v3] imx8/ls10xx: Use a sane SYS_MALLOC_F_LEN default
Date: Sat, 26 Mar 2022 11:47:40 -0300 [thread overview]
Message-ID: <20220326144740.1166027-1-festevam@gmail.com> (raw)
From: Fabio Estevam <festevam@denx.de>
When adding new features to imx8m boards, such as DM clock support,
the malloc area can be exhausted.
To avoid such issue, provide a reasonable default for the
SYS_MALLOC_F_LEN size.
Quoting Tom Rini:
"This seems to be an area where everyone is either:
- Kicking the value up a bit for themselves
- Having hard to figure out problems booting the platform because it's
too small a value until they see someone else picked a larger value.
So lets raise these a bit and get some acks, please."
Suggested-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Signed-off-by: Fabio Estevam <festevam@denx.de>
Tested-by: Adam Ford <aford173@gmail.com> #imx8mm-beacon, imx8mn-beacon
Tested-by: Heiko Thiery <heiko.thiery@gmail.com>
---
Changes since v2:
- Also bump the default for imx8/layerscape - Tom
- Expand the Cc list - Tom
Kconfig | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/Kconfig b/Kconfig
index 9dd9ec7f6dfb..8b346894e581 100644
--- a/Kconfig
+++ b/Kconfig
@@ -232,10 +232,10 @@ config SYS_MALLOC_F_LEN
depends on SYS_MALLOC_F
default 0x1000 if AM33XX
default 0x4000 if SANDBOX
- default 0x2000 if (ARCH_IMX8 || ARCH_IMX8M || ARCH_MX7 || \
- ARCH_MX7ULP || ARCH_MX6 || ARCH_MX5 || \
- ARCH_LS1012A || ARCH_LS1021A || ARCH_LS1043A || \
- ARCH_LS1046A || ARCH_QEMU || ARCH_SUNXI || ARCH_OWL)
+ default 0x2000 if (ARCH_MX7 || ARCH_MX7ULP || ARCH_MX6 || ARCH_MX5 || \
+ ARCH_QEMU || ARCH_SUNXI || ARCH_OWL)
+ default 0x10000 if (ARCH_IMX8 || ARCH_IMX8M || ARCH_LS1012A || \
+ ARCH_LS1021A || ARCH_LS1043A || ARCH_LS1046A)
default 0x400
help
Before relocation, memory is very limited on many platforms. Still,
--
2.25.1
next reply other threads:[~2022-03-26 14:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-26 14:47 Fabio Estevam [this message]
2022-04-07 14:22 ` [PATCH v3] imx8/ls10xx: Use a sane SYS_MALLOC_F_LEN default Tom Rini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220326144740.1166027-1-festevam@gmail.com \
--to=festevam@gmail.com \
--cc=aford173@gmail.com \
--cc=festevam@denx.de \
--cc=heiko.thiery@gmail.com \
--cc=marcel.ziswiler@toradex.com \
--cc=mingkai.hu@nxp.com \
--cc=priyanka.jain@nxp.com \
--cc=sbabic@denx.de \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox