summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorUlf Hansson <ulf.hansson@oss.qualcomm.com>2026-09-14 17:01:39 +0200
committerUlf Hansson <ulfh@kernel.org>2026-09-17 15:30:58 +0200
commit2224d686e788d6ad3af4cc48bbf68723f8abd326 (patch)
treeeb77ddf09063f95c943f1d7d8eb581f730f14ed3 /tools/perf/scripts/python
parent9e8dff8e097814e4d7c65cd211ccb1e2fceb460a (diff)
pmdomain: core: Add a genpd config to support unknown initial status
It's not always possible for a genpd provider to know the initial status for its corresponding PM domain(s). To register the PM domain in a safe state, the genpd provider driver may therefore have to initialize the genpd's status to be powered off, as a way to prevent the PM domain from being used when it actually could be powered off. In these cases we may end up to power on a PM domain through the genpd subsystem, while from the HW point of view it may already be powered on. Under these circumstances, it may also be required to keep the PM domain powered on until all the consumer devices have been probed. In other words, until the ->sync_state() callback for the genpd provider in question have been called. To support this behaviour for a genpd provider, let's introduce a new genpd configuration, GENPD_FLAG_POWER_UNKNOWN. Reported-by: Maulik Shah <maulik.shah@oss.qualcomm.com> Link: https://lore.kernel.org/all/20260811-domain_off_ss3-v1-0-6a0a0fc023f5@oss.qualcomm.com/ Reviewed-by: Abel Vesa <abel.vesa@oss.qualcomm.com> Tested-by: Yuanfang Zhang <yuanfang.zhang@oss.qualcomm.com> Reviewed-by: Dhruva Gole <goledhruva@gmail.com> Signed-off-by: Ulf Hansson <ulf.hansson@oss.qualcomm.com> Signed-off-by: Ulf Hansson <ulfh@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions