From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: u-boot@lists.denx.de
Subject: [PATCH] arm: actions: increase SYS_MALLOC_F_LEN
Date: Mon, 9 Nov 2020 19:48:06 +0530 [thread overview]
Message-ID: <20201109141806.GL24289@work> (raw)
In-Reply-To: <1604930468-4229-1-git-send-email-amittomer25@gmail.com>
On Mon, Nov 09, 2020 at 07:31:08PM +0530, Amit Singh Tomar wrote:
> after commit 4ab3817ff16a ("clk: fixed-rate: Enable DM_FLAG_PRE_RELOC flag")
> Cubieboard7 (based on actions S700 SoC) fails to boot.
>
> It is due to the fact that the default value of CONFIG_SYS_MALLOC_F_LEN (0x400)
> would not provide enough memory for clock device to probe (before relocation)
> well.
>
> This commit fixes it, by increasing SYS_MALLOC_F_LEN to value 0x2000.
>
> Suggested-by: Andre Przywara <andre.przywara@arm.com>
> Signed-off-by: Amit Singh Tomar <amittomer25@gmail.com>
Thanks for fixing!
Reviewed-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Regards,
Mani
> ---
> Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Kconfig b/Kconfig
> index c94b10e9fa72..6dc20ed25b29 100644
> --- a/Kconfig
> +++ b/Kconfig
> @@ -200,7 +200,7 @@ config SYS_MALLOC_F_LEN
> 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_LS1046A || ARCH_QEMU || ARCH_SUNXI || ARCH_OWL)
> default 0x400
> help
> Before relocation, memory is very limited on many platforms. Still,
> --
> 2.7.4
>
next prev parent reply other threads:[~2020-11-09 14:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 14:01 [PATCH] arm: actions: increase SYS_MALLOC_F_LEN Amit Singh Tomar
2020-11-09 14:18 ` Manivannan Sadhasivam [this message]
2020-11-09 22:20 ` 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=20201109141806.GL24289@work \
--to=manivannan.sadhasivam@linaro.org \
--cc=u-boot@lists.denx.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