stpmic1-regulator warnings

[UVV]

Hey there,

I have a custom stm32mp153c based board. I adapted bootloaders/optee/kernel from scarthgap branch of meta-st-stm32mp and have everything booting (tf-a 2.8, u-boot 2022.10, optee 3.19, kernel 6.1.28). The only remaining warnings I have are these:

root@stm32mp1:~# dmesg | grep pmic
[ 0.459590] stpmic1 2-0033: PMIC Chip Version: 0x21
[ 0.497690] stpmic1-regulator 5c009000.i2c:stpmic@33:regulators: Failed to create device link (0x180) with 2-0033
[ 0.506580] stpmic1-regulator 5c009000.i2c:stpmic@33:regulators: Failed to create device link (0x180) with 2-0033
[ 0.516882] stpmic1-regulator 5c009000.i2c:stpmic@33:regulators: Failed to create device link (0x180) with 2-0033

 

I found only two threads mentioning the issue, but couldn't figure out how to fix it and even got an impression that these are somehow expected?

https://community.st.com/t5/stm32-mpus-embedded-software-and/platform-5a001000-display-controller-deferred-probe-pending-why/m-p/710943

https://community.st.com/t5/stm32-mpus-products/various-issues-when-starting-kernel-on-custom-stm32mp151aac/m-p/598410

 

Any hints where the warnings come from?

 

Thanks,

Vyacheslav

[PatrickF]

Hi @UVV 

Scarthgap is not yet supported by OpenSTLinux (will come soon).

Wait few weeks or go back to Mickeldore: https://wiki.st.com/stm32mpu/wiki/STM32_MPU_ecosystem_release_note#OpenSTLinux_for_Arm-C2-AE_Cortex-C2-AE-A

Regards.

[UVV]

Perhaps I was not clear with my statement, but I don't use scarthgap branch, I'm still on kirkstone. I only took the bootloader/kernel from the scarthgap branch. I see that kernel version mentioned in your link is newer though. I could give it a try.

 

As a yocto maintainer, I'm not sure I like your advise to use non LTS version, and why updates are provided in mickeldore rather than in LTS branch.

[PatrickF]

Hi,

I'm not SW expert, just try to find out rationale of your warning messages.

We provide a new ecosystem major release almost every year, but as Yocto LTS is every two years, we then have one intermediate release on a 'non-LTS' Yocto version.

If you want only LTS Yocto, as you do, you should stick to our latest Kirkstone release https://wiki.st.com/stm32mpu-ecosystem-v4/wiki/STM32_MPU_ecosystem_release_note#OpenSTLinux_-28Arm-C2-AE_Cortex-C2-AE-A7-29

I guess it is important to have TF-A, OpTee and uBoot versions aligned to our ecosystem releases.

Regards.