diff options
| author | Huisong Li <lihuisong@huawei.com> | 2025-02-20 11:08:32 +0800 |
|---|---|---|
| committer | Guenter Roeck <linux@roeck-us.net> | 2025-03-02 10:31:26 -0800 |
| commit | 0ea627381eb527a0ebd262c690c3992085b87ff4 (patch) | |
| tree | 0792801190760de3e31ec524b98a9780e10af46a /tools/perf/scripts/python/export-to-sqlite.py | |
| parent | 9fee7d19bab635f89223cc40dfd2c8797fdc4988 (diff) | |
hwmon: (acpi_power_meter) Fix the fake power alarm reporting
We encountered a problem that a fake power alarm is reported to
user on the platform unsupported notifications at the second step
below:
1> Query 'power1_alarm' attribute when the power capping occurs.
2> Query 'power1_alarm' attribute when the power capping is over
and the current average power is less then power cap value.
The root cause is that the resource->power_alarm is set to true
at the first step. And power meter use this old value to show
the power alarm state instead of the current the comparison value.
Signed-off-by: Huisong Li <lihuisong@huawei.com>
Link: https://lore.kernel.org/r/20250220030832.2976-1-lihuisong@huawei.com
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions