ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion | IRC log http://irclog.whitequark.org/linux-rockchip | Community GH https://github.com/linux-rockchip | Rockchip GH https://github.com/rockchip-linux | ML https://groups.google.com/group/linux-rockchip
maze-BUG1 has joined #linux-rockchip
maze-BUG has quit [Ping timeout: 256 seconds]
maze-BUG1 is now known as maze-BUG
warpme_ has quit [Quit: Connection closed for inactivity]
_whitelogger has joined #linux-rockchip
vstehle has quit [Ping timeout: 260 seconds]
lerc has joined #linux-rockchip
kaspter has quit [Ping timeout: 256 seconds]
kaspter has joined #linux-rockchip
maze-BUG has quit [Read error: Connection reset by peer]
_whitelogger has joined #linux-rockchip
kaspter has quit [Remote host closed the connection]
kaspter has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
JohnDoe_71Rus has joined #linux-rockchip
kaspter has quit [Ping timeout: 258 seconds]
kaspter has joined #linux-rockchip
paulk-leonov has quit [Ping timeout: 246 seconds]
paulk-leonov has joined #linux-rockchip
vstehle has joined #linux-rockchip
anarsoul has quit [Read error: Connection reset by peer]
anarsoul has joined #linux-rockchip
kaspter has quit [Ping timeout: 265 seconds]
kaspter has joined #linux-rockchip
JohnDoe_71Rus has quit [Ping timeout: 272 seconds]
JohnDoe_71Rus has joined #linux-rockchip
vicencb has joined #linux-rockchip
mayab76 has joined #linux-rockchip
cristian_c has quit [Read error: Connection reset by peer]
cristian_c has joined #linux-rockchip
cristian_c has quit [Read error: Connection reset by peer]
ldevulder__ has quit [Remote host closed the connection]
cristian_c has joined #linux-rockchip
ldevulder__ has joined #linux-rockchip
<nomis> robmur01: oh great.
matthias_bgg has joined #linux-rockchip
sb35 has joined #linux-rockchip
camus1 has joined #linux-rockchip
kaspter has quit [Ping timeout: 256 seconds]
camus1 is now known as kaspter
warpme_ has joined #linux-rockchip
stikonas has joined #linux-rockchip
robmur01 has quit [Quit: robmur01]
cristian_c has quit [Read error: Connection reset by peer]
cristian_c has joined #linux-rockchip
field^Mop has joined #linux-rockchip
maze-BUG has joined #linux-rockchip
robmur01 has joined #linux-rockchip
<nomis> robmur01: *sigh* it still doesn't help me here.
<nomis> I see the 400khz clock on the clock pin, but no trace at all from the 100MHz clock.
<robmur01> boo... still, no output at all is curious. My initial thoughts there would be something off in the clock tree, or possibly something related to 3V/1.8V switching
<robmur01> what if you remove any UHS caps and just let it run in high-speed mode? (50MHz@3V)
* robmur01 carefully tweaks commit message with `git commit --amend` then sends the previously-generated patch anyway... sigh...
<robmur01> and `git send-email ... @~1` is just beyond the edge of my comfort zone most of the time :)
<nomis> robmur01: the thing is, it works with the rockchip kernel. I don't think there is any hardware related possibility.
<nomis> and I've been surveying all the clock specifications. Maybe I just fail to see an obvious difference, but that all reads sane to me.
<nomis> [ 4.026965] dwmmc_rockchip ff5f0000.dwmmc: All phases bad!
<nomis> [ 4.027874] mmc2: error -5 whilst initialising SDIO card
<nomis> [ 4.027470] mmc2: tuning execution failed: -5
<nomis> the android kernel ends up with a phase of 135
<robmur01> if it's not the clock itself, it could be that the I/O voltage disappears or the IOVSEL gets out-of-sync if the mode involves a nominal voltage switch. Do the vqmmc_supply for the module and the vccio6_supply for the I/O domain line up, and does the regulator match reality in terms of voltage and enable pins?
<nomis> phew, not sure I understand the question or know where to check that.
<robmur01> come to think of it, I think the data lines idle high, so just verifying the voltage there against regulator_summary before and after the probe attempt ought to show up any mismatch
<nomis> the datalines seem to sit at 1.8V
<robmur01> OK, so if the I/O domain ends up in 3.3V mode it can't 'hear' the module respond
<nomis> and testing the phases seems to fail for mmc_send_tuning returning -EILSEQ
<nomis> robmur01: but the clock pin should be driven by the CPU, right? I should at least see a hint of the high frequency while the driver tries to increase the speed, or?
<robmur01> I don't really know the protocol details, but I'd assume the tuning commands have to be sent at the target clock rate
<robmur01> I'm still inclined to rule out any signal level issues first - you should have CONFIG_ROCKCHIP_IODOMAIN enabled and an io_domains node enabled in your DT with, among others, a vccio6-supply property pointing at a regulator; what's that regulator?
<nomis> robmur01: ok, that might have dropped out of my device tree. *groan*
<nomis> I guess I should have another run at the devicetree comparison between the rockchip-kernel and my kernel - this time not ignoring the stuff I don't understand.
<nomis> (currently rebuilding the image, results in a few minutes...)
<nomis> robmur01: ok, I've enabled the io-domains-Node and have set vccio6-supply to &vccio_1v8_reg (which seems to what is used in the other device tree. Unfortunately it does not seem to help with the tuning execution.
* nomis fetches himself a coffee.
klokken has quit [Remote host closed the connection]
klokken has joined #linux-rockchip
cp- has quit [Read error: Connection reset by peer]
<nomis> Wait. I messed up.
cp- has joined #linux-rockchip
<nomis> it is too easy to use references wrong. There is a huge difference between "... = &someting" and "... = <&something>"
<nomis> [ 1.535741] mmc2: new ultra high speed SDR104 SDIO card at address 0001
<nomis> robmur01: I owe you something. I'd never have found that.
<robmur01> heh, at least it looked like the communication problem that it was. The "failed to reset DMA" or whatever it is you get with the wrong GMAC I/O voltage was far more of a headscratcher ;)
klokken has quit [Remote host closed the connection]
klokken has joined #linux-rockchip
cristian__c has joined #linux-rockchip
cristian_c has quit [Read error: Connection reset by peer]
lerc has quit [Ping timeout: 272 seconds]
lerc has joined #linux-rockchip
cristian__c has quit [Read error: Connection reset by peer]
cristian_c has joined #linux-rockchip
<nomis> robmur01: just for my own understanding: Is this io_domains relevant for configuring the logic-level thresholds for certain pins?
<robmur01> yup, in most cases the power for the actual I/O pads comes in from outside, so logic high is "whatever the supply is", and there's a switch between nominal 3.3V and 1.8V modes for input threshold.
klokken has quit [Remote host closed the connection]
klokken has joined #linux-rockchip
vicencb has quit [Quit: Leaving.]
vicencb has joined #linux-rockchip
robmur01 has quit [Remote host closed the connection]
robmur01 has joined #linux-rockchip
warpme_ has quit [Quit: Connection closed for inactivity]
vicencb has quit [Quit: Leaving.]
vicencb has joined #linux-rockchip
warpme_ has joined #linux-rockchip
JohnDoe_71Rus has quit [Quit: KVIrc 5.0.0 Aria http://www.kvirc.net/]
maze-BUG1 has joined #linux-rockchip
maze-BUG has quit [Ping timeout: 265 seconds]
maze-BUG1 is now known as maze-BUG
matthias_bgg has quit [Quit: Leaving]
mayab76 has quit [Ping timeout: 240 seconds]
ldevulder_ has joined #linux-rockchip
ldevulder__ has quit [Ping timeout: 260 seconds]
maze-BUG has quit [Ping timeout: 265 seconds]
maze-BUG has joined #linux-rockchip
sb35 has quit [Ping timeout: 264 seconds]
vicencb has quit [Quit: Leaving.]