crabbedhaloablut has quit [Remote host closed the connection]
crabbedhaloablut has joined #linux-rockchip
cp- has joined #linux-rockchip
alpernebbi has joined #linux-rockchip
macc24 has quit [Quit: WeeChat 3.1]
macc24 has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
sphalerite has joined #linux-rockchip
<sphalerite>
Hi folks! I'd like to get suspend working on my (rk3399) gru-bob chromebook. Currently, it seems to enter suspend just fine (last message on the serial console is "[ 251.716121] printk: Suspending console(s) (use no_console_suspend to debug)" but doesn't seem to wake up, nothing showing on the serial. Does anyone have any suggestions on how I might be able to debug this?
<macc24>
sphalerite: on what kernel?
<macc24>
why are you not using cadmium on it?
<sphalerite>
macc24: mainline 5.12
<sphalerite>
What's cadmium? :)
<macc24>
sphalerite: can you try on 5.13?
<sphalerite>
Yep can do.
<sphalerite>
Oh hi alpernebbi ! You emailed me a couple months ago about your u-boot display patches, and I didn't have the time to test them because of my move — I have some time again, what's the state of that work now?
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
<mmind00>
sphalerite: hmm I do remember testing this recently on a gru-kevin with 5.13-something I think and it did suspend and wake up again ... caveat, coreboot firmware is of the tftp-variant as that device lives in my boardfarm
<macc24>
works for me too
<macc24>
on 5.12-rc5 that i'm avoiding upgrading lol
<mps>
sphalerite: suspend/resume works also for me on gru-kevin chromebook
<mps>
5.12
<sphalerite>
I have a coreboot+u-boot firmware, maybe that could be the issue?
<macc24>
sphalerite: as long as your display is not initialized or it is de-initialized when loading kernel it would be fine
<macc24>
boot firmware doesn't really have much to do with suspend
<macc24>
as it should jump ASAP to resume vector
<macc24>
and afaict payload doesn't matter when resuming
<alpernebbi>
sphalerite: hi! most display patches are merged to u-boot, I think gru-bob should only need some config changes and maybe dt fixes.
<macc24>
o/ alpernebbi
<alpernebbi>
I got sidetracked a bit in the meanwhile, but give me a day or two and I'll rebase my branches and ask you to test if that's OK.
<alpernebbi>
o/
<alpernebbi>
macc24: I'll ping you too for kevin :D
<macc24>
alpernebbi: sure, now that school is gone i have more time to spend doing linux >:D
psydroid is now known as psydroid[m]
matthias_bgg has quit [Read error: Connection reset by peer]
<sphalerite>
hrm, WiFi seems to be broken on 5.13. And I'm getting a lot of `[ 128.845678] mmc_host mmc0: Bus speed (slot 0) = 300000Hz (slot req 300000Hz, actual 300000HZ div = 0) ` (with frequencies 400000, 300000, 200000, 100000) on the serial, but that's the case with 5.12 too.
matthias_bgg has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
<mps>
sphalerite: macc24: right, wifi is broken and I posted bug report to maintainers about two weeks age but didn't got any answer, yet
<mps>
s/age/ago/
LinuxHackerman has joined #linux-rockchip
<mps>
macc24: thanks for url, will try it later in evening
<sphalerite>
macc24: hm ok. What else might I want to check out to work out what's going wrong then? As mentioned, I don't get anything when trying to wake it up.
<sphalerite>
What might be worth mentioning also is that the power LED stays on, so it might not be suspending correctly in the first place?
<macc24>
hmm
<macc24>
how are you suspending?
psydroid[m] is now known as psydroid
<sphalerite>
systemctl suspend
<macc24>
*shrugs* works for me
<macc24>
mmind00: do you have any idea?
<sphalerite>
Hm, I thought maybe it's related to the device tree, because I thought it was using one built-in to u-boot, but no, u-boot is loading one that ships with linux from the boot partition.
<mmind00>
sphalerite: hmm so there is a uboot involved there too?
<sphalerite>
yes
<sphalerite>
coreboot loads u-boot (no depthcharge involved), u-boot loads linux
<mmind00>
which would be my first choice for a possible culprit then
<sphalerite>
What would you suggest, then? I don't want to use depthcharge since it doesn't provide a boot menu, nor anywhere near as much control over what gets booted overall…
<mmind00>
sphalerite: no clue ... but I guess in a first step try with stock coreboot+depthcharge to check if that is really the culprut
<mmind00>
culprit
<macc24>
bl31 firmware hmm
<sphalerite>
mmind00: I'd have to completely trash my installation for that since I don't have partitions available for the depthcharge approach >_<
<sphalerite>
macc24: ooh, good point
<macc24>
sphalerite: you can just boot from usb pendrive
<sphalerite>
hm, I've tried setting the gbb flags on a stock firmware image to 0x4039 and flashing that. It's not recognising the kernel I put on a partition on an SD card (I'm pressing Ctrl+U to try booting it) but also not outputting anything on the serial even though the relevant bit is set? What might I be doing wrong?
<macc24>
sphalerite: what serial
<sphalerite>
macc24: the AP serial via suzyqable
<macc24>
ha, finally tracked down someone with it
<sphalerite>
:)
<sphalerite>
I wouldn't be flashing around so happy-go-lucky without it :D
<macc24>
well
<macc24>
on those machines you can just use soic8 clip some of the time
<sphalerite>
aah fair enough. I don't like opening it :)
<sphalerite>
(and I also don't have a SOIC8 clip nor the corresponding programmer)
armoon has joined #linux-rockchip
<sphalerite>
mmind00: alright, finally managed to try it with depthcharge, same result