search

compulab-yokneam / meta-bsp-imx8mm

16 stars 21 forks source link

iot-gate-imx8 - Device tree issues on boot #28

Closed Dominik-Helfenstein closed 9 months ago

Dominik-Helfenstein commented 10 months ago

Hello, when booting I get the following log. Note that several components fail to look up, especially

2023-09-11T11:31:54.515746+00:00 meshgw-bbgpp kernel: [    0.831143] imx8m_pm_domain power-domains:hsiomix-pd: Looking up power-supply from device tree
2023-09-11T11:31:54.515749+00:00 meshgw-bbgpp kernel: [    0.831154] imx8m_pm_domain power-domains:hsiomix-pd: Looking up power-supply property in node /power-domains/hsiomix-pd failed
2023-09-11T11:31:54.515752+00:00 meshgw-bbgpp kernel: [    0.831255] imx8m_pm_domain power-domains:pcie-pd: Looking up power-supply from device tree
2023-09-11T11:31:54.515758+00:00 meshgw-bbgpp kernel: [    0.831264] imx8m_pm_domain power-domains:pcie-pd: Looking up power-supply property in node /power-domains/pcie-pd failed
2023-09-11T11:31:54.515762+00:00 meshgw-bbgpp kernel: [    0.831366] imx8m_pm_domain power-domains:usbotg1-pd: Looking up power-supply from device tree
2023-09-11T11:31:54.515764+00:00 meshgw-bbgpp kernel: [    0.831375] imx8m_pm_domain power-domains:usbotg1-pd: Looking up power-supply property in node /power-domains/usbotg1-pd failed
2023-09-11T11:31:54.515767+00:00 meshgw-bbgpp kernel: [    0.831473] imx8m_pm_domain power-domains:usbotg2-pd: Looking up power-supply from device tree
2023-09-11T11:31:54.515769+00:00 meshgw-bbgpp kernel: [    0.831484] imx8m_pm_domain power-domains:usbotg2-pd: Looking up power-supply property in node /power-domains/usbotg2-pd failed
2023-09-11T11:31:54.515772+00:00 meshgw-bbgpp kernel: [    0.831580] imx8m_pm_domain power-domains:gpumix-pd: Looking up power-supply from device tree
2023-09-11T11:31:54.515779+00:00 meshgw-bbgpp kernel: [    0.831589] imx8m_pm_domain power-domains:gpumix-pd: Looking up power-supply property in node /power-domains/gpumix-pd failed
2023-09-11T11:31:54.515782+00:00 meshgw-bbgpp kernel: [    0.831713] imx8m_pm_domain power-domains:vpumix-pd: Looking up power-supply from device tree
2023-09-11T11:31:54.515784+00:00 meshgw-bbgpp kernel: [    0.831722] imx8m_pm_domain power-domains:vpumix-pd: Looking up power-supply property in node /power-domains/vpumix-pd failed
2023-09-11T11:31:54.515787+00:00 meshgw-bbgpp kernel: [    0.831816] imx8m_pm_domain power-domains:vpug1-pd: Looking up power-supply from device tree
2023-09-11T11:31:54.515789+00:00 meshgw-bbgpp kernel: [    0.831825] imx8m_pm_domain power-domains:vpug1-pd: Looking up power-supply property in node /power-domains/vpug1-pd failed
2023-09-11T11:31:54.515792+00:00 meshgw-bbgpp kernel: [    0.831925] imx8m_pm_domain power-domains:vpug2-pd: Looking up power-supply from device tree
2023-09-11T11:31:54.515799+00:00 meshgw-bbgpp kernel: [    0.831938] imx8m_pm_domain power-domains:vpug2-pd: Looking up power-supply property in node /power-domains/vpug2-pd failed
2023-09-11T11:31:54.515802+00:00 meshgw-bbgpp kernel: [    0.832035] imx8m_pm_domain power-domains:vpuh1-pd: Looking up power-supply from device tree
2023-09-11T11:31:54.515805+00:00 meshgw-bbgpp kernel: [    0.832044] imx8m_pm_domain power-domains:vpuh1-pd: Looking up power-supply property in node /power-domains/vpuh1-pd failed
2023-09-11T11:31:54.515808+00:00 meshgw-bbgpp kernel: [    0.832148] imx8m_pm_domain power-domains:dispmix-pd: Looking up power-supply from device tree
2023-09-11T11:31:54.515811+00:00 meshgw-bbgpp kernel: [    0.832157] imx8m_pm_domain power-domains:dispmix-pd: Looking up power-supply property in node /power-domains/dispmix-pd failed
2023-09-11T11:31:54.515814+00:00 meshgw-bbgpp kernel: [    0.832278] imx8m_pm_domain power-domains:mipi-pd: Looking up power-supply from device tree
2023-09-11T11:31:54.516418+00:00 meshgw-bbgpp kernel: [    0.832289] imx8m_pm_domain power-domains:mipi-pd: Looking up power-supply property in node /power-domains/mipi-pd failed
2023-09-11T11:31:54.517050+00:00 meshgw-bbgpp kernel: [    1.180205] sdhci-pltfm: SDHCI platform and OF driver helper
2023-09-11T11:31:54.517052+00:00 meshgw-bbgpp kernel: [    1.187161] sdhci-esdhc-imx 30b60000.mmc: Looking up vmmc-supply from device tree
2023-09-11T11:31:54.517054+00:00 meshgw-bbgpp kernel: [    1.187177] sdhci-esdhc-imx 30b60000.mmc: Looking up vmmc-supply property in node /soc@0/bus@30800000/mmc@30b60000 failed
2023-09-11T11:31:54.517057+00:00 meshgw-bbgpp kernel: [    1.187214] sdhci-esdhc-imx 30b60000.mmc: Looking up vqmmc-supply from device tree
2023-09-11T11:31:54.517060+00:00 meshgw-bbgpp kernel: [    1.187222] sdhci-esdhc-imx 30b60000.mmc: Looking up vqmmc-supply property in node /soc@0/bus@30800000/mmc@30b60000 failed
2023-09-11T11:31:54.517867+00:00 meshgw-bbgpp kernel: [    1.605299] rohm-bd718x7 1-004b: Looking up buck6-supply property in node /soc@0/bus@30800000/i2c@30a30000/bd71837@4b failed
2023-09-11T11:31:54.517876+00:00 meshgw-bbgpp kernel: [    1.605351] LDO5: supplied by regulator-dummy
2023-09-11T11:31:54.517879+00:00 meshgw-bbgpp kernel: [    1.610503] LDO6: will resolve supply early: buck7
2023-09-11T11:31:54.517874+00:00 meshgw-bbgpp systemd[1]: Finished Bind mount volatile /srv.
2023-09-11T11:31:54.517882+00:00 meshgw-bbgpp kernel: [    1.610510] rohm-bd718x7 1-004b: Looking up buck7-supply from device tree
2023-09-11T11:31:54.517884+00:00 meshgw-bbgpp kernel: [    1.610542] rohm-bd718x7 1-004b: Looking up buck7-supply property in node /soc@0/bus@30800000/i2c@30a30000/bd71837@4b failed
2023-09-11T11:31:54.517887+00:00 meshgw-bbgpp kernel: [    1.610587] LDO6: supplied by regulator-dummy
2023-09-11T11:31:54.517889+00:00 meshgw-bbgpp kernel: [    1.614960] regulator-dummy: could not add device link regulator.26: -ENOENT
2023-09-11T11:31:54.517891+00:00 meshgw-bbgpp kernel: [    1.615538] LDO6: 900 <--> 1800 mV at 1200 mV, enabled
2023-09-11T11:31:54.517888+00:00 meshgw-bbgpp systemd[1]: Starting Load/Save Random Seed...
2023-09-11T11:31:54.517904+00:00 meshgw-bbgpp kernel: [    1.616071] LDO7: 1800 <--> 3300 mV at 1800 mV, disabled
2023-09-11T11:31:54.517900+00:00 meshgw-bbgpp systemd[1]: Finished Load/Save Random Seed.
2023-09-11T11:31:54.517907+00:00 meshgw-bbgpp kernel: [    1.616857] at24 1-0050: Looking up vcc-supply from device tree
2023-09-11T11:31:54.517909+00:00 meshgw-bbgpp kernel: [    1.616867] at24 1-0050: Looking up vcc-supply property in node /soc@0/bus@30800000/i2c@30a30000/eeprom@50 failed
2023-09-11T11:31:54.517912+00:00 meshgw-bbgpp kernel: [    1.616914] at24 1-0050: supply vcc not found, using dummy regulator
2023-09-11T11:31:54.517914+00:00 meshgw-bbgpp kernel: [    1.624178] at24 1-0050: 1024 byte 24c08 EEPROM, writable, 16 bytes/write
2023-09-11T11:31:54.517917+00:00 meshgw-bbgpp kernel: [    1.631052] i2c i2c-1: IMX I2C adapter registered
2023-09-11T11:31:54.517913+00:00 meshgw-bbgpp systemd[1]: First Boot Complete was skipped because of a failed condition check (ConditionFirstBoot=yes).
2023-09-11T11:31:54.517926+00:00 meshgw-bbgpp kernel: [    1.637432] imx6q-pcie 33800000.pcie: Looking up epdev_on-supply from device tree
2023-09-11T11:31:54.517930+00:00 meshgw-bbgpp kernel: [    1.637455] imx6q-pcie 33800000.pcie: Looking up epdev_on-supply property in node /soc@0/pcie@33800000 failed
2023-09-11T11:31:54.517933+00:00 meshgw-bbgpp kernel: [    1.637543] imx6q-pcie 33800000.pcie: supply epdev_on not found, using dummy regulator
2023-09-11T11:31:54.517927+00:00 meshgw-bbgpp systemd-udevd[289]: Using default interface naming scheme 'v250'.
2023-09-11T11:31:54.517936+00:00 meshgw-bbgpp kernel: [    1.637590] 30860000.serial: ttymxc0 at MMIO 0x30860000 (irq = 38, base_baud = 5000000) is a IMX
2023-09-11T11:31:54.517938+00:00 meshgw-bbgpp kernel: [    1.645824] imx6q-pcie 33800000.pcie: Looking up vpcie-supply from device tree
2023-09-11T11:31:54.517940+00:00 meshgw-bbgpp kernel: [    1.654275] imx6q-pcie 33800000.pcie: Looking up vpcie-supply property in node /soc@0/pcie@33800000 failed
2023-09-11T11:31:54.517941+00:00 meshgw-bbgpp systemd-udevd[285]: Using default interface naming scheme 'v250'.
2023-09-11T11:31:54.517950+00:00 meshgw-bbgpp kernel: [    1.654319] imx6q-pcie 33800000.pcie: Looking up vph-supply from device tree
2023-09-11T11:31:54.517953+00:00 meshgw-bbgpp kernel: [    1.654327] imx6q-pcie 33800000.pcie: Looking up vph-supply property in node /soc@0/pcie@33800000 failed
2023-09-11T11:31:54.517956+00:00 meshgw-bbgpp kernel: [    1.654373] imx6q-pcie 33800000.pcie: EXT REF_CLK is used!.
2023-09-11T11:31:54.517959+00:00 meshgw-bbgpp kernel: [    1.656614] fec 30be0000.ethernet: Looking up phy-supply from device tree
2023-09-11T11:31:54.517962+00:00 meshgw-bbgpp kernel: [    1.659993] fec 30be0000.ethernet: Looking up phy-supply property in node /soc@0/bus@30800000/ethernet@30be0000 failed

I see that they are mostly initialized later successfully. For example, vmmc-supply fails at 1.1s but succeeds at 1.8s. I don't have these issues on zeus, this is kirkstone.

Full log: syslog-kirkstone-boot-errors.log

Device tree: sb-iotgimx8-kirkstone.dts.txt

kkapranov commented 9 months ago

Hello Dominik,

The annoying messages are printed, since DEBUG_KERNEL feature is set in the kernel config; no real regression was found.

Dominik-Helfenstein commented 9 months ago

Thank you