From: Sean Anderson <seanga2@gmail.com>
To: Heiko Thiery <heiko.thiery@gmail.com>, Simon Glass <sjg@chromium.org>
Cc: Heinrich Schuchardt <xypron.glpk@gmx.de>,
Tom Rini <trini@konsulko.com>, Stefano Babic <sbabic@denx.de>,
Fabio Estevam <festevam@gmail.com>, Peng Fan <peng.fan@nxp.com>,
U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: [PATCH v2] board: kontron: increase the CONFIG_SYS_MALLOC_F_LEN
Date: Wed, 23 Mar 2022 14:33:12 -0400 [thread overview]
Message-ID: <19e21ec5-184b-10d9-9bee-8ece6dc58095@gmail.com> (raw)
In-Reply-To: <CAEyMn7ZsF9F8UOf8Q6UtFcuvUmq8kOYhmH-fu-38px-=C_b2eQ@mail.gmail.com>
On 3/23/22 2:26 PM, Heiko Thiery wrote:
> Hi Simon,
>
> Am Mi., 23. März 2022 um 19:04 Uhr schrieb Simon Glass <sjg@chromium.org>:
>>
>> Hi Heinrich,
>>
>> On Tue, 22 Mar 2022 at 03:25, Heinrich Schuchardt <xypron.glpk@gmx.de> wrote:
>>>
>>> On 3/21/22 15:26, Heiko Thiery wrote:
>>>> It was observed that enabling additional DM modules the configured
>>>> malloc value is not sufficient. So lets increase the value.
>>>>
>>>> Signed-off-by: Heiko Thiery <heiko.thiery@gmail.com>
>>>> ---
>>>> v2:
>>>> - add a more proper commit message to explan why the value was increased
>>>>
>>>> configs/kontron_pitx_imx8m_defconfig | 1 +
>>>> 1 file changed, 1 insertion(+)
>>>>
>>>> diff --git a/configs/kontron_pitx_imx8m_defconfig b/configs/kontron_pitx_imx8m_defconfig
>>>> index 76430213e3..30c3586937 100644
>>>> --- a/configs/kontron_pitx_imx8m_defconfig
>>>> +++ b/configs/kontron_pitx_imx8m_defconfig
>>>> @@ -2,6 +2,7 @@ CONFIG_ARM=y
>>>> CONFIG_ARCH_IMX8M=y
>>>> CONFIG_SYS_TEXT_BASE=0x40200000
>>>> CONFIG_SYS_MALLOC_LEN=0x600000
>>>> +CONFIG_SYS_MALLOC_F_LEN=0x10000
>>>
>>> @Heiko
>>> Should we really adjust this on board level? Won't we have the same
>>> problem on all imx8m boards?
>>>
>>> Why don't you change the default for all i.mx8 boards in /Kconfig?
>>>
>>> @Tom, @Simon
>>> Shouldn't we replace the default of 0x400 by 0x2000 generally?
>>
>> I don't think that is a good idea. That is a lot of memory! Many
>> platforms don't need that much.
>>
>> I wonder what is driving this large amount. Is it pinctrl?
>
> The increase comes from the introduction of a clock driver for the
> imx8mq platform.
Yes, the problem is that CCF creates a udevice+clk+private data for
every clock. This runs about 150-200 bytes per clock on a 64-bit
platform. In addition, many physical clocks are modeled as several
logical clocks plus a composite. This means a platform with maybe
20-30 physical clocks can easily allocate 10k-20k to create
the clock tree.
--Sean
next prev parent reply other threads:[~2022-03-23 18:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 14:26 [PATCH v2] board: kontron: increase the CONFIG_SYS_MALLOC_F_LEN Heiko Thiery
2022-03-21 14:30 ` Fabio Estevam
2022-03-22 9:25 ` Heinrich Schuchardt
2022-03-22 12:25 ` Tom Rini
2022-03-22 12:34 ` Heiko Thiery
2022-03-23 13:14 ` Tom Rini
2022-03-23 14:09 ` Adam Ford
2022-03-23 18:04 ` Simon Glass
2022-03-23 18:26 ` Heiko Thiery
2022-03-23 18:33 ` Sean Anderson [this message]
2022-03-23 18:49 ` Tom Rini
2022-03-23 18:53 ` Simon Glass
2022-03-23 18:59 ` Tom Rini
2022-03-23 19:38 ` Simon Glass
2022-03-23 18:53 ` Simon Glass
2022-03-23 19:19 ` Sean Anderson
2022-03-23 19:38 ` Simon Glass
2022-03-23 20:03 ` Adam Ford
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=19e21ec5-184b-10d9-9bee-8ece6dc58095@gmail.com \
--to=seanga2@gmail.com \
--cc=festevam@gmail.com \
--cc=heiko.thiery@gmail.com \
--cc=peng.fan@nxp.com \
--cc=sbabic@denx.de \
--cc=sjg@chromium.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.