kevery has quit [Remote host closed the connection]
kevery has joined #linux-rockchip
ldevulder_ is now known as ldevulder
kaspter has quit [Read error: Connection reset by peer]
kaspter has joined #linux-rockchip
inode has joined #linux-rockchip
kaspter has quit [Ping timeout: 240 seconds]
kaspter has joined #linux-rockchip
ganbold has quit [Quit: Leaving]
ldevulder has quit [Quit: Leaving]
ldevulder has joined #linux-rockchip
<mmind00>
BenG83: maybe kevery has an idea about that?
<kevery>
Well, I can check if I can reproduce the issue.
<mmind00>
thanks :-)
<kevery>
BenG83: Which board do you use?
<kevery>
mmind00: You are welcome :)
<kevery>
BenG83: Is the suspend issue a new one, or the first time run this case?
kevery has quit [Ping timeout: 268 seconds]
<robmur01>
I've nominally tried, but my nanopc-t4 doesn't even get that far since one of the USB drivers refuses to suspend at all :(
field^Zzz4 has joined #linux-rockchip
field^Zzz4 has quit [Client Quit]
elektirnis has joined #linux-rockchip
ganbold has joined #linux-rockchip
BenG83 has joined #linux-rockchip
<BenG83>
kevery, this is on Pinebook Pro
<BenG83>
I have not tried to suspend on my RockPro64
<BenG83>
suspend works with bsp kernel/atf
jaganteki has quit [Remote host closed the connection]
<BenG83>
this happens with kernel 5.5 and mainline ATF
<BenG83>
probably have to trace where in the ATF the exception happens
<BenG83>
can anyone try suspend on a different RK3399 board maybe?
return0__ has joined #linux-rockchip
return0e_ has quit [Ping timeout: 268 seconds]
leah2 has quit [Ping timeout: 252 seconds]
leah2 has joined #linux-rockchip
kevery has joined #linux-rockchip
vicencb has joined #linux-rockchip
BenG83 has quit [Ping timeout: 268 seconds]
vicencb has quit [Quit: Leaving.]
vicencb has joined #linux-rockchip
BenG83 has joined #linux-rockchip
kevery has quit [Ping timeout: 240 seconds]
leah2 has quit [Ping timeout: 248 seconds]
BenG83 has quit [Quit: Leaving]
ldevulder_ has joined #linux-rockchip
leah2 has joined #linux-rockchip
ldevulder has quit [Ping timeout: 268 seconds]
ldevulder has joined #linux-rockchip
ldevulder_ has quit [Ping timeout: 260 seconds]
ldevulder_ has joined #linux-rockchip
ldevulder has quit [Ping timeout: 268 seconds]
ldevulder_ has quit [Remote host closed the connection]
ldevulder_ has joined #linux-rockchip
ldevulder_ has quit [Ping timeout: 260 seconds]
jlandafk is now known as jlanda
ldevulder_ has joined #linux-rockchip
ldevulder_ has quit [Ping timeout: 240 seconds]
ganbold has quit [Ping timeout: 268 seconds]
<anarsoul>
I have strong suspicion that you may need rk808 driver in ATF to get it working
<mmind00>
looking at an objdump of the vendor atf .elf that looks to be true ... various i2c functions and also a suspicious pmic_lp_set function ;-)
<mmind00>
The rk3399-gru devices had the advantage of not having a programmable pmic, hence mainline atf is missing these parts
<robmur01>
although switching to SLEEP mode is the one thing RK808 *does* have a simple pin for, and the reference design even wires it up to a GPIO :D
<robmur01>
not to mention the SYR8xx supplies too
<anarsoul>
yet we need to pass gpio numbers to ATF somehow
<robmur01>
plat_get_rockchip_suspend_gpio() ?
<robmur01>
plus I guess there's always the option of doing stuff from the M0 instead
<anarsoul>
robmur01: we need to teach it to parse dts
<anarsoul>
IIRC it doesn't do that atm
<robmur01>
I thought that stuff was passed in from SPL?
<robmur01>
(or rather coreboot)
lerc has quit [Quit: No Ping reply in 180 seconds.]
lerc has joined #linux-rockchip
<mmind00>
ATF does parse the devicetree
<mmind00>
i.e. uboot generally provides a its dt as platform param to atf and we get for example the choose node from there to determine the uart
<mmind00>
coreboot does have it's own structure to transmit data to atf though ... so that param is either nothing, a coreboot struct or a dt pointer