narmstrong changed the topic of #linux-amlogic to: Amlogic mainline kernel development discussion - our wiki http://linux-meson.com/ - ml linux-amlogic@lists.infradead.org - Publicly Logged on https://irclog.whitequark.org/linux-amlogic
return0e_ has joined #linux-amlogic
return0e has quit [Ping timeout: 256 seconds]
sputnik_ has joined #linux-amlogic
etrig has joined #linux-amlogic
vagrantc has quit [Quit: leaving]
sputnik_ has quit [Remote host closed the connection]
return0e_ has quit [Remote host closed the connection]
return0e_ has joined #linux-amlogic
ldevulder_ has quit [Ping timeout: 240 seconds]
return0e_ has quit [Ping timeout: 246 seconds]
return0e has joined #linux-amlogic
Barada has joined #linux-amlogic
buzzmarshall has quit [Remote host closed the connection]
return0e has quit [Remote host closed the connection]
return0e has joined #linux-amlogic
return0e has quit [Read error: Connection reset by peer]
Elpaulo has quit [Quit: Elpaulo]
sputnik_ has joined #linux-amlogic
Barada has quit [Quit: Barada]
afaerber has quit [Remote host closed the connection]
afaerber has joined #linux-amlogic
chewitt has quit [Quit: Adios!]
drieschel has joined #linux-amlogic
ldevulder_ has joined #linux-amlogic
ldevulder_ has quit [Client Quit]
random_yanek has quit [Ping timeout: 250 seconds]
random_yanek has joined #linux-amlogic
ldevulder has joined #linux-amlogic
Barada has joined #linux-amlogic
return0e has joined #linux-amlogic
sputnik_ has quit [Remote host closed the connection]
sputnik_ has joined #linux-amlogic
sputnik_ has quit [Remote host closed the connection]
sputnik_ has joined #linux-amlogic
jmasson has joined #linux-amlogic
jmasson has left #linux-amlogic [#linux-amlogic]
Darkmatter66 has quit [Ping timeout: 256 seconds]
Darkmatter66 has joined #linux-amlogic
Darkmatter66 has quit [Ping timeout: 256 seconds]
Darkmatter66 has joined #linux-amlogic
Darkmatter66 has quit [Ping timeout: 246 seconds]
Darkmatter66 has joined #linux-amlogic
Darkmatter66 has quit [Ping timeout: 246 seconds]
Darkmatter66 has joined #linux-amlogic
jelly-home is now known as jelly
random_yanek has quit [Ping timeout: 252 seconds]
repk has quit [Quit: WeeChat 2.7.1]
repk has joined #linux-amlogic
random_yanek has joined #linux-amlogic
sputnik_ has quit [Ping timeout: 256 seconds]
_whitelogger has joined #linux-amlogic
wildea01 has quit [Quit: leaving]
wildea01 has joined #linux-amlogic
Barada has quit [Quit: Barada]
buzzmarshall has joined #linux-amlogic
The_Coolest has quit [Ping timeout: 268 seconds]
The_Coolest has joined #linux-amlogic
phh has quit [Ping timeout: 265 seconds]
return0e has quit [Remote host closed the connection]
phh has joined #linux-amlogic
yann has quit [Ping timeout: 264 seconds]
yann has joined #linux-amlogic
GNUtoo has quit [Ping timeout: 260 seconds]
GNUtoo has joined #linux-amlogic
steev has quit [*.net *.split]
steev has joined #linux-amlogic
steev has quit [Max SendQ exceeded]
steev has joined #linux-amlogic
psydruid has quit [Ping timeout: 260 seconds]
drieschel has quit [Quit: drieschel]
psydruid has joined #linux-amlogic
vagrantc has joined #linux-amlogic
jmasson has joined #linux-amlogic
<etrig> still hunting for relevant information, but does somebody know if there are any outstanding issues with SD cards on odroid-c2?
<etrig> running linux 5.5.11 and my board almost never reboots successfully, having tried three different cards
<etrig> thinking it might be related to tflash_vdd and tf_io regulators, but not having any success with my device tree modifications yet
<repk> etrig: Does it boot fine with the same card when you plug unplug power ?
<etrig> repk: it does
<etrig> repk: only on reboot specifically do I get things like "fs_devread read error - block" in u-boot
<repk> etrig: hm weird
<etrig> I was running u-boot 2019.04 and just upgraded to 2020.01 to be sure
jmasson has quit [Quit: Using Circe, the loveliest of all IRC clients]
damex has quit [Ping timeout: 250 seconds]
Yardanico has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
Yardanico has joined #linux-amlogic
Yardanico has quit [Client Quit]
Yardanico has joined #linux-amlogic
Yardanico has quit [Client Quit]
Yardanico has joined #linux-amlogic
repk has quit [Quit: WeeChat 2.7.1]
repk has joined #linux-amlogic
sputnik_ has joined #linux-amlogic
return0e has joined #linux-amlogic
Darkmatter66_ has joined #linux-amlogic
Darkmatter66 has quit [Ping timeout: 246 seconds]
<xdarklight> the tflash_vdd regulator also exists on Odroid-C2 but it doesn't have the regulator-always-on; property there
<xdarklight> please try setting it and report back
<etrig> xdarklight: that's what inspired me to try with tflash_vdd and then also tf_io, but it didn't seem to make a difference
<etrig> unfortunately all three of my cards are sandisk brand and maybe all share the same problem
<xdarklight> etrig: hmm, can you drop all the sd-uhs-* modes from sd_emmc_b and try again?
<xdarklight> maybe Linux leaves tf_io at 1.8V and then the bootrom gets confused
<etrig> xdarklight: I'll try that, thanks
<xdarklight> (without the sd-uhs-* mode the card IO will stay at 3.3V)
<etrig> does "regulator-boot-on" have any value here?
<xdarklight> AFAIK no
<etrig> and should I also be rebuilding u-boot with these device tree changes?
Pix has quit [Quit: ZNC - http://znc.sourceforge.net]
Pix has joined #linux-amlogic
<xdarklight> I'm not sure about what u-boot does and what not. if doesn't take much effort then it's worth trying
<xdarklight> it's interesting that the bootrom can actually read u-boot from SD card but then it fails in u-boot
<etrig> wonder if it's a clock issue rather than a voltage issue
<etrig> since a reboot occasionally works
<etrig> xdarklight: two successful reboots by dropping sd-uhs-*
<xdarklight> can you check the GPIOs used by the two regulators in u-boot?
<xdarklight> if those look good then you are probably right with your suspicion that it's a clock issue (or a card/controller interoperability issue)
<etrig> I tried enabling just sd-uhs-sdr12 and immediately hit the issue again
<etrig> looks like this was a problem on the vendor's fork as well: https://forum.odroid.com/viewtopic.php?f=141&t=25070