imx8mq allocation issue

[Peng Fan]

On 9/12/2022 3:48 PM, Heiko Thiery wrote:
> Hi Peng,
> 
> Am Mo., 12. Sept. 2022 um 09:26 Uhr schrieb Peng Fan <peng.fan at oss.nxp.com>:
>>
>>
>>
>> On 9/9/2022 5:12 PM, Heiko Thiery wrote:
>>> HI,
>>>
>>> I think on the imx8mq platform we have a problem with the introduction
>>> of the clock driver. I tried to debug the problem that the pitx-imx8m
>>> board was not able to start for some time. I was wondering why the
>>> pitx-im8m doesn't work anymore although the imx8mq_evk is running.
>>>
>>> So I switched to the imx8mq_evk for counter testing. As I already
>>> figured out in [1] also the imx8mq_evk is not able to start properly.
>>>
>>> On the EVK I enabled the DEBUG_UART and see the outputs below. I
>>> suspect all imx8mq boards have this problem.
>>>
>>> CONFIG_DEBUG_UART_BASE=0x30860000      # for uart1
>>> CONFIG_DEBUG_UART_CLOCK=24000000
>>>
>>> --- 8< ----
>>> U-Boot SPL 2022.10-rc4-00038-ge3fce5e560-dirty (Sep 09 2022 - 10:51:29 +0200)
>>> PMIC:  PFUZE100 ID=0x10
>>> SEC0:  RNG instantiated
>>> Normal Boot
>>> Trying to boot from MMC2
>>> clk_register: failed to get <NULL> device (parent of ckil)
>>> clk_register: failed to get <NULL> device (parent of clock-osc-27m)
>>> alloc space exhausted
>>> alloc space exhausted
>>> alloc space exhausted
>>> alloc space exhausted
>>
>> Seems SPL_DM_CLK consumes the malloc space, so you meet such error.
>>
> 
> I dont think the SPL is the problem. Because the output appears after
> "Trying to boot from MMC2".

oh, it maybe CONFIG_MALLOC_F_ADDR and CONFIG_VAL(SYS_MALLOC_F_LEN) not
large enough for DM CLK with DM_FLAG_PRE_RELOC?

Regards,
Peng.

>