rperier has quit [Remote host closed the connection]
rperier has joined #linux-rockchip
tizbac has joined #linux-rockchip
fischerm has quit [Ping timeout: 252 seconds]
lkcl has quit [Ping timeout: 264 seconds]
cnxsoft has joined #linux-rockchip
lkcl has joined #linux-rockchip
cnxsoft has quit [Read error: Connection reset by peer]
cnxsoft1 has joined #linux-rockchip
cnxsoft1 is now known as cnxsoft
lkcl has quit [Ping timeout: 240 seconds]
lkcl has joined #linux-rockchip
shahid_ has joined #linux-rockchip
Guest33281 has quit [Ping timeout: 260 seconds]
geekerlw has quit [Ping timeout: 260 seconds]
wadim_ has joined #linux-rockchip
shahid_ has quit [Ping timeout: 260 seconds]
shahid_ has joined #linux-rockchip
shahid_ has quit [Ping timeout: 260 seconds]
shahid_ has joined #linux-rockchip
geekerlw has joined #linux-rockchip
Aussie_matt has joined #linux-rockchip
dlezcano has quit [Ping timeout: 240 seconds]
vagrantc has joined #linux-rockchip
vagrantc has quit [Quit: leaving]
dlezcano has joined #linux-rockchip
nighty has quit [Quit: Disappears in a puff of smoke]
mrjay has joined #linux-rockchip
<mrjay>
about mmc bug ... its power management patches that cousing problem. Driver doesn't wake up correctly. As a workaround comment all pm_runtime* lines from b/drivers/mmc/host/dw_mmc-rockchip.c
<stdint>
mrjay, thanks you
<stdint>
would you like to submit a patch
<stdint>
I was thinking the same thing
<mrjay>
stdint: i don't know the couse of the problem ... i only figured out a dirty workaround :) ... so no patch now
<stdint>
you could send it first and see whether any other could fix it
<stdint>
or I could try at weekend
<mrjay>
stdint: there is no point sending patch commenting pm_runtime* ... it won't be accepted. We need to find out what is the root problem. But i know to little about dw_mmc to investigate :(
<stdint>
mrjay, I would suggest you to send out a dirty workaround making more people joined to find out that what the problem is
<mrjay>
stdint: i will poke around a little more
<mrjay>
stdint: on what board do you see mmc bug ? rk3288?
<stdint>
mrjay, rk3288 firefly
<stdint>
firefly reload
<mrjay>
stdint: thanks
<phh>
mrjay: what's your problem precisely? it never boots at all?
<phh>
I'm asking because on my chromebook c201, on 4.9, the device boots perhaps 50% of time
<phh>
mmc is detected, but it is still waiting for root
<phh>
(on sdcard)
<wadim_>
I have no mmc boot problems with 4.9
<mrjay>
stdint: same here but 100% of the time ... pm is the problem
<stdint>
yes, 100% time
<phh>
wadim_: c201 too?
<wadim_>
no, with a custom rk3288 based board
nighty has joined #linux-rockchip
mrjay has quit [Quit: Page closed]
dlezcano has quit [Remote host closed the connection]
dlezcano has joined #linux-rockchip
dlezcano has quit [Remote host closed the connection]