ChanServ changed the topic of #linux-msm to:
flamingradian has joined #linux-msm
flamingradian has quit []
Danct12 has joined #linux-msm
marvin24_ has joined #linux-msm
marvin24 has quit [Ping timeout: 480 seconds]
flamingradian[m] has joined #linux-msm
<falconhash[m]> Never depend on a single income to get financial freedom. I can teach you how you can earn from $5,000 to $6,000 weekly,without sending money to me or anyone, but you will pay me 10% commission when you receive your profit. if you are interested, ask me how via Whatsapp
<falconhash[m]> 👇👇👇
<falconhash[m]> +1 (570) 801-0862
falconhash[m] has quit [autokilled: Spambot. Mail support@oftc.net if you think this is in error. (2022-07-27 04:32:45)]
jhovold has joined #linux-msm
pevik has joined #linux-msm
Daanct12 has joined #linux-msm
Danct12 has quit [Read error: Connection reset by peer]
Daanct12 has quit [Remote host closed the connection]
<Mis012[m]> matrix spam? please no...
pespin has joined #linux-msm
<lumag> Marijn[m], konradybcio: do you know if anybody tried using PSCI_DOMAIN idle states on 8994/8998?
<lumag> This boils down to the question whether OSI is supported on them or not.
<lumag> and the same question goes to the sdm630/660
<lumag> kholk[m], ^^
qyousef has joined #linux-msm
qyousef has quit [Ping timeout: 480 seconds]
qyousef has joined #linux-msm
qyousef has quit [Ping timeout: 480 seconds]
qyousef has joined #linux-msm
qyousef has quit [Ping timeout: 480 seconds]
pevik has quit [Ping timeout: 480 seconds]
qyousef has joined #linux-msm
<aka_[m]> <lumag> "This boils down to the question..." <- can linux determine that?
<aka_[m]> on 8976 there is something like that in log:
<aka_[m]> psci: OSI mode supported.
<lumag> aka_[m], do you have CONFIG_PSCI_DOMAINS on?
<aka_[m]> not even config_psci enabled it appears
<lumag> aka_[m], then if you don't see dmesg errors from CPUidle or PSCI, then OSI is supported
<lumag> and psci_domains should work as expected
<aka_[m]> there is
<aka_[m]> but i bet i haven't configured it well
<aka_[m]> CPUidle PSCI: failed to enable OSI mode: -95
<lumag> aka_[m], ah, so it means that it also doesn't want the CPU_SUSPEND.
<lumag> Let me send the debugging patch...
<aka_[m]> at first glance 8953 also fails with same error
<lumag> could you please check with this patch if/when you have time.
<aka_[m]> that might take a lot of time, maybe once i dig into 8976 once again.
jhovold has quit [Ping timeout: 480 seconds]
<lumag> aka_[m], n/p
<lumag> I'm trying to understand, how common is this firmware issue
<Mis012[m]> the real firmware issue is that secure boot fuses are provisioned by someone other than the end user on most devices
<Mis012[m]> every other firmware issue could be solved if one could change the fw...
pespin has quit [Remote host closed the connection]
<konradybcio> lumag: 8994 psci is broken at best, i don't have high hopes
<konradybcio> that said i don't think anybody tried
<konradybcio> 8998.. i don't think anybody tried but i'd be surprised if it didn't work there
<lumag> konradybcio, what is broken with 8994 (just curious)?
<konradybcio> what isn't..
<konradybcio> psci is partially implemented on some fws and not implemented on others
<lumag> For the 8998 the question is about the OSI vs SET_SUSPEND_MODE support
<konradybcio> it's barely good enough to start secondary cores
<konradybcio> IIRC somebody said it can't even shut them down
<konradybcio> on xperias, no psci at all on 8994
<lumag> I see.
<lumag> So they must use SPM, which is forbidden for arm64?
<konradybcio> bingo
<konradybcio> and you can't implement psci-hvc because qHYP
<konradybcio> there is however an exploit that lets you take over hypervisor
<konradybcio> but sony patched it out even on pre-release-reviewers-journalists fw
qyousef has quit [Quit: WeeChat 2.8]
qyousef has joined #linux-msm
qyousef has quit [Quit: Updating details, brb]
qyousef has joined #linux-msm
diederik has left #linux-msm [Going to see what happens IRL, see ya!]