<macromorgan>
does anyone have an issue with that or thoughts? The reason is that I need to specify a less-than-generic name in order to use alsa ucm rules
<LinuxHackerman[m>
I guess I'll just throw the gru patches from cadmium at my kernel and see if it makes everything better
<macc24>
those patches are not really related
<LinuxHackerman[m>
aww
<macc24>
they are in cadmium sources to fix/workaround issue with kevin panel not refreshing randomly
<macc24>
idk can't remember
<LinuxHackerman[m>
ok
<LinuxHackerman[m>
what's the thing to use on a gru nowadays firmware-wise? I'm using coreboot with u-boot as payload, but maybe that isn't the most sensible option?
stikonas has joined #linux-rockchip
<macc24>
alpernebbi worked on that
<macc24>
i currently just use stock boot firmware
lurchi__ is now known as lurchi_
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
lurchi_ is now known as lurchi__
<alpernebbi>
LinuxHackerman[m: I use coreboot with u-boot payload as well, I got display stuff etc merged in by u-boot 2022.04 so you might want to refresh your build :D
<LinuxHackerman[m>
oh nice
<LinuxHackerman[m>
trying that just now, but it's not detecting the eMMC anymore...
<LinuxHackerman[m>
wait no that was with 2021.10, just about to try 2022.04
<LinuxHackerman[m>
Wow! It does work!
<LinuxHackerman[m>
It's beautiful 🤩
<LinuxHackerman[m>
and the eMMC regression from 2021.10 is fixed too, so it boots!
<LinuxHackerman[m>
thanks for doing that alpernebbi!
<alpernebbi>
np, glad things work on gru-bob as well :D
<LinuxHackerman[m>
Hm. Now does anyone have suspend working on a gru of some description? I'm on mainline 5.17.9 right now and it just wakes up again instantly when I try to suspend
<LinuxHackerman[m>
(which I guess is somewhat nice, because previously it would go to sleep and never wake up)
<LinuxHackerman[m>
hm, same behaviour with both s2idle and deep sleep
<LinuxHackerman[m>
oh but it no longer reboots :(
<LinuxHackerman[m>
only cold boot seems to work
<alpernebbi>
suspend seems to work on my gru-kevin
<LinuxHackerman[m>
hm ok
<LinuxHackerman[m>
what about rebooting?
<alpernebbi>
yep, reboots fine as well
<LinuxHackerman[m>
hm. For me it doesn't seem to get to u-boot on reboot
<LinuxHackerman[m>
... and this time it rebooted fine (with my build again)!?
<LinuxHackerman[m>
need to go out briefly, I'll be back later
<alpernebbi>
I'll probably go to sleep
<alpernebbi>
but tpm is different between gru-kevin and gru-bob
<alpernebbi>
it might need something special that isn't being done
<LinuxHackerman[m>
So given that the reboot problem isn't that much of a problem... Does anyone know how I can get Linux to tell me what woke it back up from suspend?
Rathann has joined #linux-rockchip
psydroid2 has quit [Ping timeout: 240 seconds]
amazingfate_ has joined #linux-rockchip
amazingfate has quit [Ping timeout: 244 seconds]
<smaeul>
you can try `cat /sys/power/pm_wakeup_irq` or /sys/kernel/debug/wakeup_sources, or you can compare /proc/interrupts before and after suspend
<smaeul>
those first two files will only be updated if the IRQ that caused wakeup was one that Linux _expected_ to be the wakeup source