After installing image and for faster boot time adding “quiet” to U-Boot defargs variable. The problem is I see new unexpected dmesg error compared to quarterly 5.3.0:
[ 0.085457] reg-fixed-voltage regulator-module-3v3-eth: Failed to register regulator: -517
-517 bedeutet EPROBE_DEFER and probe-defer mean that it is not ready in the boot process. With this error the driver tells the kernel: please try again later. later more things are booted and it will work.
This is a mechanism in the kernel to order different drivers during the boot process. But every thing is fine.
It is not so nice of cause there are still these messages during quiet mode.
Thank you very much for explanation. How do I know it succeeds probing later? If it is OK to delay probe, why then it attracts attention as if it was not OK? Something isn’t right here. Is it really “failed” as message says or indeed just “warning, we hoped it would take faster, but it had to be delayed for no reason”? I’m not blaming anyone for this, but it is indeed yet another linux/driver/DT/etc defect
What exactly is the issue?
Is something not working or are you just worried about the message?
Which carrier board are you using?
Did you try this on one of Toradex’s carrier boards?
What exactly is the issue?
New error message in dmesg, new compared to former Toradex Linux BSP’s.
Is something not working or are you just worried about the message?
Worried + additional boot time output on serial console leads to longer boot time, not much longer but indeed longer.
Which carrier board are you using?
Custom, Iris V1.1A, Aster V1.1
Did you try this on one of Toradex’s carrier boards?
yes