summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/stackcollapse.py
diff options
context:
space:
mode:
authorMike Tipton <mike.tipton@oss.qualcomm.com>2026-06-29 13:33:36 -0700
committerUlf Hansson <ulfh@kernel.org>2026-07-13 12:32:27 +0200
commit7178817f190496f2bfdec181fb4aa72832448468 (patch)
tree6d3a6ac49ca040ccb8a0d64f3054884373ebc423 /tools/perf/scripts/python/stackcollapse.py
parenta1d9d3b958d69a13783613304f524f489fecdd1f (diff)
pmdomain: qcom: rpmhpd: Skip retention by default
Retention is very rarely an operational corner. In the majority of cases, HW cannot operate properly at Retention levels and so the minimum operational level when enabling a rail is the first corner above Retention. A small subset of always-on use cases can operate at Retention, but those aren't controlled from HLOS. Currently, we allow Retention by default and only disallow it special cases. But this leaves us open to various failures when the PD is enabled without first being voted to an OPP above Retention. Such as when a child GDSC PD requests to enable its parent RPMh PD. In this case, the GDSC would get stuck powering on. Newer chips have started supporting Retention on rails that didn't previously (such as for MMCX). Instead of adding more special cases to skip Retention on MMCX, start skipping Retention by default since it's almost never desired from an HLOS perspective. Signed-off-by: Mike Tipton <mike.tipton@oss.qualcomm.com> Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com> Signed-off-by: Ulf Hansson <ulfh@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions