kevery has quit [Read error: Connection reset by peer]
kevery1 is now known as kevery
nashpa has quit [Ping timeout: 265 seconds]
dliviu has joined #linux-rockchip
dliviu has quit [Ping timeout: 248 seconds]
lurchi_ has joined #linux-rockchip
dliviu has joined #linux-rockchip
lurchi__ has quit [Ping timeout: 264 seconds]
naoki has quit [Ping timeout: 252 seconds]
digetx has quit [Quit: No Ping reply in 180 seconds.]
digetx has joined #linux-rockchip
naoki has joined #linux-rockchip
dliviu has quit [Ping timeout: 248 seconds]
dliviu has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
vagrantc has quit [Quit: leaving]
naoki has quit [Ping timeout: 255 seconds]
stikonas has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 252 seconds]
kevery1 is now known as kevery
naoki has joined #linux-rockchip
hanetzer has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Read error: Connection reset by peer]
kevery1 is now known as kevery
kevery has quit [Ping timeout: 268 seconds]
camus has quit [Read error: Connection reset by peer]
camus has joined #linux-rockchip
lurchi_ has quit [Quit: Konversation terminated!]
lurchi_ has joined #linux-rockchip
lurchi_ is now known as lurchi__
<warpme>
guys: i'm playing with 3588 rock-5b on mainline 6.1.9 + https://github.com/neggles/linux-quartz64/commits/linux-quartz64. Kernel boots, i see usb, eth (partially), pci-e are appearing in dmesg - but can't move forward due issue with sd-card. My dt mmc fragment is the same like in radxa bsp dt. I verified both regulators related to mmc. Boot stops like this: https://pastebin.com/iAewpEYD Lowering max-frequency nor disabling
<warpme>
sd-uhs-sdr104 cap. not hepls. Maybe somebody has some hints how to move forward with this?
camus has quit [Quit: camus]
chewitt has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
<macromorgan>
I had problems with sdmmc on the 3566 too until I set those properly
Tenkawa has quit [Quit: Was I really ever here?]
<macromorgan>
I think some parent clocks of the MMC controller weren't set properly on my 3566, when I set the values correctly it started to work. Possible the 3588 is the same way?
<macromorgan>
though I think I also do some funkiness in U-Boot, since I'm using mainline U-Boot too (again for the 3566)
<macromorgan>
so bottom line... look at your clock rates on a device that works (see what's in /sys/kernel/debug/clk/clk_summary) and make sure your PLL clocks match to the best of your ability
<macromorgan>
if that doesn't fix it look at the other clocks that relate to the mmc. If that still doesn't fix it... then... I dunno.
vagrantc has joined #linux-rockchip
naoki has quit [Quit: naoki]
<macromorgan>
I'm lazily waiting for SoC support (not necessarily support for the Rock 5B explicitly) in U-Boot, then I'll start dev in earnest on mine. For now I'm mopping up work on the 3568 series.
Daaanct12 has quit [Quit: Quitting]
Danct12 has joined #linux-rockchip
Daanct12 has joined #linux-rockchip
Danct12 has quit [Ping timeout: 252 seconds]
lurchi__ is now known as lurchi_
Daaanct12 has joined #linux-rockchip
Daanct12 has quit [Ping timeout: 252 seconds]
lurchi_ has quit [Quit: Konversation terminated!]
lurchi_ has joined #linux-rockchip
lurchi_ is now known as lurchi__
Tenkawa has joined #linux-rockchip
lurchi__ is now known as lurchi_
lurchi_ has quit [Remote host closed the connection]