imx8mq allocation issue

[Peng Fan]

On 9/13/2022 3:25 PM, Heiko Thiery wrote:
> Hi Peng,
> 
> Am Di., 13. Sept. 2022 um 09:00 Uhr schrieb Peng Fan <peng.fan at oss.nxp.com>:
>>
>>
>>
>> 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".
>> Do you have time to give a try?
>>
>> diff --git a/configs/imx8mq_evk_defconfig b/configs/imx8mq_evk_defconfig
>> index cf207295e54..14b49ab5906 100644
>> --- a/configs/imx8mq_evk_defconfig
>> +++ b/configs/imx8mq_evk_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=0x2800
>>    CONFIG_SPL_GPIO=y
>>    CONFIG_SPL_LIBCOMMON_SUPPORT=y
>>    CONFIG_SPL_LIBGENERIC_SUPPORT=y
>> @@ -36,7 +37,7 @@ CONFIG_SPL_BSS_START_ADDR=0x180000
>>    CONFIG_SPL_BSS_MAX_SIZE=0x2000
>>    CONFIG_SPL_BOARD_INIT=y
>>    # CONFIG_SPL_SHARES_INIT_SP_ADDR is not set
>> -CONFIG_SPL_STACK=0x187ff0
>> +CONFIG_SPL_STACK=0x188000
>>    CONFIG_SYS_SPL_MALLOC=y
>>    CONFIG_HAS_CUSTOM_SPL_MALLOC_START=y
>>    CONFIG_CUSTOM_SYS_SPL_MALLOC_ADDR=0x42200000
>> diff --git a/include/configs/imx8mq_evk.h b/include/configs/imx8mq_evk.h
>> index ea4305667f2..728b4f7e665 100644
>> --- a/include/configs/imx8mq_evk.h
>> +++ b/include/configs/imx8mq_evk.h
>> @@ -16,8 +16,6 @@
>>    /*#define CONFIG_ENABLE_DDR_TRAINING_DEBUG*/
>>    #define CONFIG_SYS_SPL_PTE_RAM_BASE    0x41580000
>>
>> -/* malloc f used before GD_FLG_FULL_MALLOC_INIT set */
>> -#define CONFIG_MALLOC_F_ADDR           0x182000
>>    /* For RAW image gives a error info not panic */
>>
>>    #define CONFIG_POWER_PFUZE100
>>
> 
> This has no positive effect.

Just posted a fix: "imx8mq_evk: enlarge SYS_MALLOC_F_LEN"

Thanks,
Peng.

> 
> 
> By the way: I have to remove the hdmi_phy node. Otherwise the board is
> no longer able to start:
> 
> --- 8< ---
> U-Boot SPL 2022.10-rc4-00038-ge3fce5e560-dirty (Sep 13 2022 - 09:20:21 +0200)
> pmic_alloc: No available memory for allocation!
> power_pfuze100_init: POWER allocation error!
> SEC0:  RNG instantiated
> Normal Boot
> Trying to boot from MMC2
> þ
> U-Boot SPL 2022.10-rc4-00038-ge3fce5e560-dirty (Sep 13 2022 - 09:20:21 +0200)
> pmic_alloc: No available memory for allocation!
> power_pfuze100_init: POWER allocation error!
> SEC0:  RNG instantiated
> Normal Boot
> Trying to boot from MMC2
> :
> --- 8< ---
> 
> diff --git a/arch/arm/dts/imx8mq.dtsi b/arch/arm/dts/imx8mq.dtsi
> index 49eadb081b..e0d1fd2b02 100644
> --- a/arch/arm/dts/imx8mq.dtsi
> +++ b/arch/arm/dts/imx8mq.dtsi
> @@ -63,12 +63,12 @@
>                  clock-output-names = "osc_27m";
>          };
> 
> -       hdmi_phy_27m: clock-hdmi-phy-27m {
> -               compatible = "fixed-clock";
> -               #clock-cells = <0>;
> -               clock-frequency = <27000000>;
> -               clock-output-names = "hdmi_phy_27m";
> -       };
> +//     hdmi_phy_27m: clock-hdmi-phy-27m {
> +//             compatible = "fixed-clock";
> +//             #clock-cells = <0>;
> +//             clock-frequency = <27000000>;
> +//             clock-output-names = "hdmi_phy_27m";
> +//     };
> 
>          clk_ext1: clock-ext1 {
>                  compatible = "fixed-clock";
>