tree a04c3a2745854be39205622e04a85873a6f2eead
parent 26854617cb30f42ac76945ac3958af42814856a8
author Andrew Geissler <geissonator@yahoo.com> 1660837704 -0400
committer Andrew Geissler <andrew@geissonator.com> 1661454335 +0000

power-restore: always honor AlwaysOn policy

An internal bug was opened recently noting that when the
only-run-apr-on-power-loss config option was set, the AlwaysOn policy
was not executed. This didn't make sense because the AlwaysOn policy is
specifically saying to always power the system on. This commit changes
the logic to always power on, no matter what, if the user has set the
policy to AlwaysOn.

This change fixes a subtle bug in the one-time logic as well. Prior
to this change, the one-time setting would always be executed even if
the only-run-apr-on-power-loss config option was set. The reasoning
behind the bug was that the one-time did need to always be executed,
when it was set to AlwaysOn. The one-time is used in situations where
host or BMC firmware needs to reboot the BMC but ensure the system boots
back up after the BMC reboot (inband code update, brownout conditions).
This commit ensures we continue to execute that behavior but also
ensures we do not run the one-time otherwise when
only-run-apr-on-power-loss is set and there was not an AC loss.

Tested:
  - Verified AlwaysOn always powered on system
  - Verified power was only "Restored" when there was an AC loss

Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Ic5ba84cf2d4fe80fc60ebf9440520a80d91c9ed9