Hi Heiko,
On 2022-03-15 08:35, Heiko Thiery wrote:
Hi Angus and all,
Am Di., 15. März 2022 um 14:09 Uhr schrieb Angus Ainslie <an...@akkea.ca>:
This is a DM clock driver based off the imx8mm u-boot driver and
the linux
kernel driver.
All of the PLLs and clocks are initialized so the subsystems below are
functional and tested.
1) USB host and peripheral
2) ECSPI
3) UART
4) I2C all busses
5) USDHC for eMMC support
6) USB storage
7) GPIO
8) DRAM
Snip
when adding this patch and enabling CLK_IMX8MQ I see the following on
my board .. Any idea what I missed here?
--- >8 ---
U-Boot SPL 2022.04-rc4-00008-g390d9bf9a1 (Mar 15 2022 - 16:26:59 +0100)
Trying to boot from SD card
U-Boot 2022.04-rc4-00008-g390d9bf9a1 (Mar 15 2022 - 16:26:59 +0100)
CPU: Freescale i.MX8MQ rev2.1 at 800 MHz
Reset cause: POR
Model: Kontron pITX-imx8m
DRAM: alloc space exhausted
alloc space exhausted
alloc space exhausted
alloc space exhausted
alloc space exhausted
alloc space exhausted
alloc space exhausted
alloc space exhausted
alloc space exhausted
alloc space exhausted
alloc space exhausted
alloc space exhausted
4 GiB
My guess is that there was static code that was setting up the DRAM pll
that isn't get executed now that there's a DM clock driver.
I'd try enabling DEBUG in the clk-uclass and clk-composite drivers.
Also look at what DRAM initialization code is not being run now. Our
board doesn't have an DRAM specific initialization so there could be a
bug in the DRAM setup.
clk_register: failed to get <NULL> device (parent of ckil)
clk_register: failed to get <NULL> device (parent of sys1_pll)
clk_register: failed to get <NULL> device (parent of sys2_pll)
clk_register: failed to get <NULL> device (parent of sys3_pll)
These are warnings and shouldn't affect the functioning of the driver.
No serial driver found
Are you using the DM serial driver ?
Again this is not something that is running on our board. But I can try
enabling it.
Thanks
Angus
resetting ...
--- >8 ---
--
Heiko
