You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CPUFreq: Add policy-aware validation script with per-policy result tracking
This update replaces the per-core cpufreq walker with a more robust,
policy-aware implementation. The new script:
- Identifies cpufreq policies and associated CPU cores via sysfs
- Validates frequency scaling for each policy, using 'userspace' governor
- Logs per-policy results with PASS/FAIL based on actual frequency behavior
- Improves compatibility across SoCs with shared cpufreq domains
Signed-off-by: Srikanth Muppandam <smuppand@qti.qualcomm.com>
The `CPUFreq_Validation` test validates the CPU frequency scaling capabilities of a system using the Linux `cpufreq` subsystem. It verifies the ability to set and reflect CPU frequencies across shared policy domains (e.g., clusters of CPUs sharing frequency control).
6
+
7
+
This test is designed to be **SoC-agnostic**, supporting platforms with per-policy frequency management (e.g., Qualcomm SoCs with `policy0`, `policy4`, etc.).
8
+
9
+
## Test Goals
10
+
11
+
- Ensure all cpufreq policies are present and functional
12
+
- Iterate through all available frequencies and validate correct scaling
13
+
- Ensure that CPU governors can be set to `userspace`
14
+
- Provide robust reporting per policy (e.g., `CPU0-3 [via policy0] = PASS`)
15
+
- Avoid flaky failures in CI by using retries and proper checks
16
+
17
+
## Prerequisites
18
+
19
+
- Kernel must be built with `CONFIG_CPU_FREQ` and `CONFIG_CPU_FREQ_GOV_USERSPACE`
20
+
-`sysfs` access to `/sys/devices/system/cpu/cpufreq/*`
0 commit comments