On Thu, Feb 20, 2025 at 11:08:32AM +0800, Huisong Li wrote: > 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@xxxxxxxxxx> Applied. Guenter
