<aka_[m]>
bamse: your scripts went nuts or that huge pull was intended?
<steev>
i hope it was intended :D
<konradybcio>
aka_: QC_IMAGE_VERSION_STRING
<konradybcio>
aka_: the "mpm gpios" are lines that are wired up to the RPM subsystem, such that the vast majority of the SoC can be powered off, but e.g. usb or tsens can wake it up from total power collapse
<aka_[m]>
So device sleep and I connext usb, then interrupt is triggered and rpm wakes device up?
<konradybcio>
yes
<konradybcio>
it wakes up the AP and then your device works like usual
<aka_[m]>
And now its all good because we don't really deep sleep right?
<konradybcio>
well it's there to allow "deep sleep"
<konradybcio>
qualcomm socs can gate all the clocks and all the power lines coming to the AP and peripherals
<konradybcio>
RPM is always on as long as the device is powered on
<aka_[m]>
konradybcio: and what about other question? The pins in pinctrl comes from ds binding right?
<konradybcio>
and powered on == the battery is connected and it hasn't been powered off for good
<konradybcio>
yes from there
<aka_[m]>
Ita confusing
<konradybcio>
they shuffled it between dt and .c a few times
<aka_[m]>
PDC is some new kind of mpm?
<konradybcio>
yes PDC is essentially MPM for this purpose
<aka_[m]>
Or rpmh only
<konradybcio>
rpmh only yes
<konradybcio>
they remade the entire (low) power setup with the introduction of rpmh
<aka_[m]>
konradybcio: as you are working on multiple new socs, any idea if older misses something other than perf which makes them run uis like phosh/gnome with frame rate looking like 30 rather than 60?
<konradybcio>
define "new"
<aka_[m]>
Anything with "dpu"
<konradybcio>
anything with DPU>=5 needs changes to the cmd mode handling which Marijn is working on
<konradybcio>
video mode should be fine
<aka_[m]>
Well pleb devices like Mido or leeco so vid mode
<aka_[m]>
Maybe just a5xx is sad and that's all
<konradybcio>
and what socs are affected?
<aka_[m]>
8953,8976 aren't really snappy with cpufreq in place
<aka_[m]>
Maybe interconnects
<Marijn[m]>
kmscube?
<aka_[m]>
No just uis
<aka_[m]>
For kmscube we aren't supposed to launch it inside de?
<aka_[m]>
Or can we for testing
<konradybcio>
i don't think it will even let you
<aka_[m]>
So what we have to do?
<konradybcio>
kill de, run kmscube
<aka_[m]>
Kill de And login manager.
<aka_[m]>
Ah right
<Marijn[m]>
^
<Marijn[m]>
I want you to test if it's mdp5 or the GPU
<Marijn[m]>
IIRC mdp5 was okay, it's the GPU
<Marijn[m]>
(kmscube uses the GPU but only very slightly, if it doesn't reach 60fps defer to modetest)