diff options
| author | Viresh Kumar <[email protected]> | 2023-06-14 09:59:32 +0000 |
|---|---|---|
| committer | Viresh Kumar <[email protected]> | 2023-06-19 04:20:09 +0000 |
| commit | 7c41cdcd3bbee5d49de9d4821b15e49d155ff22b (patch) | |
| tree | 90c682ac35d71e68606a2fbee21a385881e24b20 /tools/perf/scripts/python/Perf-Trace-Util/lib | |
| parent | OPP: pstate is only valid for genpd OPP tables (diff) | |
| download | kernel-7c41cdcd3bbee5d49de9d4821b15e49d155ff22b.tar.gz kernel-7c41cdcd3bbee5d49de9d4821b15e49d155ff22b.zip | |
OPP: Simplify the over-designed pstate <-> level dance
While adding support for "performance states" in the OPP and genpd core,
it was decided to set the `pstate` field via genpd's
pm_genpd_opp_to_performance_state() helper, to allow platforms to set
`pstate` even if they don't have a corresponding `level` field in the DT
OPP tables (More details are present in commit 6e41766a6a50 ("PM /
Domain: Implement of_genpd_opp_to_performance_state()")).
Revisiting that five years later clearly suggests that it was
over-designed as all current users are eventually using the `level`
value only.
The previous commit already added necessary checks to make sure pstate
is only used for genpd tables. Lets now simplify this a little, and use
`level` directly and remove `pstate` field altogether.
Suggested-by: Ulf Hansson <[email protected]>
Signed-off-by: Viresh Kumar <[email protected]>
Reviewed-by: Ulf Hansson <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/Perf-Trace-Util/lib')
0 files changed, 0 insertions, 0 deletions