narmstrong changed the topic of #linux-amlogic to: Amlogic mainline kernel development discussion - our wiki http://linux-meson.com/ - ml linux-amlogic@lists.infradead.org - official channel moved from Freenode - publicly logged on https://libera.irclog.whitequark.org/linux-amlogic
hexdump01 has quit [Ping timeout: 246 seconds]
hexdump01 has joined #linux-amlogic
nnq has quit [*.net *.split]
ChanServ has quit [*.net *.split]
ChanServ has joined #linux-amlogic
nnq has joined #linux-amlogic
ndufresne has quit [Quit: The Lounge - https://thelounge.chat]
ndufresne has joined #linux-amlogic
ndufresne has quit [Client Quit]
ndufresne has joined #linux-amlogic
djrscally has joined #linux-amlogic
<f_> Kwiboo: A311D is g12b I thought?
<f_> g12a is S905X2 IIRC?
<Kwiboo> f_: you are correct, my initial though was that my vim3 was g12a, I trusted the output from BL31 that mentions G12A :-)
<f_> BL31 always says G12A I think
<f_> bl2 does say g12b on g12b though iirc.
<Kwiboo> yes I noticed that, my vim3 is in fact a g12b with a a311d soc after a closer look, and the radxa zero is a s905y2 (g12a) and the radxa zero2 is a a311d (g12b)
<Kwiboo> my testing on all those three have resulted in three different results :-S, vim3 could freeze due to an irq in early resume and also froze later in resume process, the zero2 (same soc) did not have an irq freeze and looked to come much longer, but still froze just after it reported resume is complete
<Kwiboo> and on the zero (g12a) everything works fine :-)
<Kwiboo> I will likely just adjust the patch message to be more accurate and still include it when I send out the series that also fixes/cleanup other parts
<f_> I'll have to give 7.1 a try when I can
<Kwiboo> f_: thanks for assisting and testing!, I will try to get the meson dw-hdmi patches out later, found a new use-after-free issue with dw-hdmi-cec so I will re-spin the initial dw-hdmi series first
psydroid2 has joined #linux-amlogic
ungeskriptet has quit [Ping timeout: 245 seconds]
ungeskriptet has joined #linux-amlogic
jbrunet has quit [Server closed connection]
jbrunet has joined #linux-amlogic
adeepn has quit [Server closed connection]
adeepn has joined #linux-amlogic
ungeskriptet_ has joined #linux-amlogic
ungeskriptet has quit [Ping timeout: 268 seconds]
ungeskriptet_ is now known as ungeskriptet
<narmstrong> I got both socs in CI, I'll try to give it a spin and try to do a suspend/resume
nnq has quit [Ping timeout: 252 seconds]
nnq has joined #linux-amlogic
psydroid2 has quit [Quit: KVIrc 5.2.6 Quasar http://www.kvirc.net/]
gis has quit [Server closed connection]
gis has joined #linux-amlogic
jelly has quit [Read error: Connection reset by peer]
jelly has joined #linux-amlogic
<josch> 👀 my irssii highlight on suspend/resume triggered -- i have a few bananapi cm4 with a311d here which would like to be able to resume (i can mail hardware to somebody if that would help)
<f_> Resume doesn't work for you?
<f_> I'll have to try on my CM4 too then
<josch> f_: yes, last time in #mnt-reform you said that the problem is that the SCP firmware that is bl30 has no idea what the reform keyboard is so it cannot be resumed via the keyboard
<f_> oh that
djrscally has quit [Ping timeout: 272 seconds]
GNUtoo has quit [Server closed connection]
GNUtoo has joined #linux-amlogic
<Kwiboo> I have now posted the drm/meson dw-hdmi series and the last patch is related to suspend/resume, I was not fully sure it that patch is needed/wanted: https://lore.kernel.org/dri-devel/20260518194744.2483580-14-jonas@kwiboo.se/
<Kwiboo> even the existing call in meson_dw_hdmi_pm_suspend() to 'Reset TOP' looks wrong, like it is taking the block out of reset instead of putting it in reset :-S
linkmauve has quit [Remote host closed the connection]
linkmauve has joined #linux-amlogic
linkmauve has quit [Remote host closed the connection]
linkmauve has joined #linux-amlogic