DC-IRC has quit [Remote host closed the connection]
DC-IRC has joined #armbian-allwinner
<DC-IRC> [Discord] <viraniac> The mmc@4020000 node seems to be there in sun50i-h616-bigtreetech-cb1-sd.dtb file. So my guess is mmc driver is failing to load for some reason. Look through the kernel/dmesg logs and see if you spot any errors related to mmc. You can allso upload the logs and serial console output on paste.armbian.com and share the link for the same. That way we would be able to look into the logs as well
<DC-IRC> [Discord] <idubrov> I added some logging to the kernel itself, barbarian style, to the drivers/mmc/host/sunxi-mmc.c
<DC-IRC> [Discord] <idubrov> What I see is that for that mmc@4020000 it fails at `ret = sunxi_mmc_resource_request(host, pdev);`
<DC-IRC> [Discord] <idubrov> I see log lines before it, but not after.
<DC-IRC> [Discord] <idubrov> For mmc@4021000, I see all my added log lines.
<DC-IRC> [Discord] <idubrov> I don't see anything other than my log lines in dmesg, though.
<DC-IRC> [Discord] <idubrov> Currently adding more logs to find where it errors out. I think, `sunxi_mmc_resource_request` returns an error.
<DC-IRC> [Discord] <idubrov> I added some logging to the kernel itself, barbarian style, to the drivers/mmc/host/sunxi-mmc.c
<DC-IRC> [Discord] <idubrov> What I see is that for that mmc@4020000 it fails at `ret = sunxi_mmc_resource_request(host, pdev);`
<DC-IRC> [Discord] <idubrov> I see log lines before it, but not after.
<DC-IRC> [Discord] <idubrov> For mmc@4021000 (other MMC device), I see all my added log lines.
<DC-IRC> [Discord] <idubrov> I don't see anything other than my log lines in dmesg, though.
<DC-IRC> [Discord] <idubrov> Okay, `ret = mmc_regulator_get_supply(host->mmc);` returns `-EPROBE_DEFER`, on 5 attempts of sunxi-mmc to initialize. Not sure what that means....
<DC-IRC> [Discord] <viraniac> That means the resources required for mmc access is not availablle at that time and driver will try again later. But I guess it ran out of the number of retries for the same
<DC-IRC> [Discord] <viraniac> are there any pinctrl errors in the logs?
<DC-IRC> [Discord] <idubrov> This is what I have in dmesg: https://paste.armbian.com/ohahazosar.yaml
<DC-IRC> [Discord] <idubrov> (these ridiculous log lines for `4020000.mmc` are the debugging I added)
<DC-IRC> [Discord] <viraniac> Two things stands out to me
<DC-IRC> [Discord] <viraniac> ```
<DC-IRC> [Discord] <viraniac> [ 1.811326] sunxi-mmc 4020000.mmc: RR: supply -517
<DC-IRC> [Discord] <viraniac> [ 1.815860] sunxi-mmc 4021000.mmc: card claims to support voltages below defined range
<DC-IRC> [Discord] <viraniac> ```
<DC-IRC> [Discord] <idubrov> The second line is about other MMC, which I don't even know what is it. I get the same log line on the kernel that does work.
<DC-IRC> [Discord] <viraniac> I think the dts needs some work, mainly the pmic node needs updating to work with upstream axp313a driver
<DC-IRC> [Discord] <viraniac> Can you try replacing &r_i2c section in arch/arm64/boot/dts/allwinner/sun50i-h616-bigtreetech-cb1.dtsi from the one present in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/arch/arm64/boot/dts/allwinner/sun50i-h616-bigtreetech-cb1.dtsi?h=v6.7.5
<DC-IRC> [Discord] <idubrov> No, the same result.
<DC-IRC> [Discord] <viraniac> ok....I cant think of anything else based on that log at this point. Probably someone else will have some suggestions. Sorry for not being able to help.
<DC-IRC> [Discord] <idubrov> YES!
<DC-IRC> [Discord] <idubrov> So, the snippet you gave me *does* contain part of the solution! I don't know why didn't it work by itself, but `reg_aldo1` should be `aldo1` and not `ldo1`. `reg_dldo1` should be `dldo1` and not `ldo2`.
<DC-IRC> [Discord] <idubrov> I found it by looking through `/sys/kernel/debug` and noticing that these two regulators were under names `0-36-aldo1` or something like that. Also, `/sys/kernel/debug/devices_deferred ` did show that `mmc` was "deferred" (but no details).
DC-IRC has quit [Read error: Connection reset by peer]