From: Tom Rini <trini@konsulko.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: sbabic@denx.de, u-boot@lists.denx.de, heiko.thiery@gmail.com,
xypron.glpk@gmx.de, aford173@gmail.com,
marcel.ziswiler@toradex.com, mingkai.hu@nxp.com,
priyanka.jain@nxp.com, Fabio Estevam <festevam@denx.de>
Subject: Re: [PATCH v3] imx8/ls10xx: Use a sane SYS_MALLOC_F_LEN default
Date: Thu, 7 Apr 2022 10:22:06 -0400 [thread overview]
Message-ID: <20220407142206.GR14282@bill-the-cat> (raw)
In-Reply-To: <20220326144740.1166027-1-festevam@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 940 bytes --]
On Sat, Mar 26, 2022 at 11:47:40AM -0300, Fabio Estevam wrote:
> 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>
Applied to u-boot/master, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2022-04-07 14:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-26 14:47 [PATCH v3] imx8/ls10xx: Use a sane SYS_MALLOC_F_LEN default Fabio Estevam
2022-04-07 14:22 ` Tom Rini [this message]
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=20220407142206.GR14282@bill-the-cat \
--to=trini@konsulko.com \
--cc=aford173@gmail.com \
--cc=festevam@denx.de \
--cc=festevam@gmail.com \
--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=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