<mwalle>
Kubu_work: and yeah, you ran into the same problem as we did. I've tried pushing TI to not hardcode the power-off sequence into PM firmware, but so far, no success.
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #linux-ti
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #linux-ti
florian_kc has joined #linux-ti
<Kubu_work>
mwalle: I may have another issue on the custom board, with your patch applied I got "ti-sci 44083000.system-controller: Mbox timedout in resp"
<Kubu_work>
Thanks for your reply :)
<Kubu_work>
Anyway I'm still using a kernel 6.1.y, I didn't tried ti-6.12.y yet (nor even latest upstream)
<mwalle>
Kubu_work: maybe another power-off handler is invoked, there is a chain of them
<Kubu_work>
I don't know, Actually I'm not 100% sure that the power-off PSCI method is really disabled
<mwalle>
Kubu_work: No I don't think it is disabled, it's just another power-off handler. I had some dt patches so you can specify a priority, but it worked for my case, so I dropped them
<Kubu_work>
mwalle: Ok, I'll have a look maybe later next week
arnd has quit [Server closed connection]
arnd has joined #linux-ti
Peng_Fan has joined #linux-ti
tlwoerner has quit [Ping timeout: 248 seconds]
tlwoerner has joined #linux-ti
tlwoerner has quit [Ping timeout: 258 seconds]
tlwoerner has joined #linux-ti
tlwoerner has quit [Ping timeout: 248 seconds]
tlwoerner has joined #linux-ti
tlwoerner has quit [Ping timeout: 260 seconds]
tlwoerner has joined #linux-ti
florian_kc has quit [Ping timeout: 260 seconds]
florian has quit [Quit: Ex-Chat]
Peng_Fan has quit [Quit: Connection closed for inactivity]
florian_kc has joined #linux-ti
jkangas has quit [Ping timeout: 255 seconds]
jkangas has joined #linux-ti
cbeznea_ has joined #linux-ti
goliath has quit [Quit: SIGSEGV]
goliath has joined #linux-ti
ungeskriptet has quit [Read error: Connection reset by peer]