diff options
| author | Thang Tran <thuutran@amperecomputing.com> | 2023-10-05 05:20:05 +0300 |
|---|---|---|
| committer | Thang Q. Nguyen <thang@os.amperecomputing.com> | 2023-10-19 05:49:20 +0300 |
| commit | 7c3ecf4c4e762c8957ca8453da98cbcd52184101 (patch) | |
| tree | e211440051a537eec2895704a3a52e4d2640c8d8 /meta-openembedded/meta-python/recipes-devtools/python/python3-process-tests_2.1.2.bb | |
| parent | 38f200f4681f0d780fbef1e2b7418ac2b33c8463 (diff) | |
| download | openbmc-7c3ecf4c4e762c8957ca8453da98cbcd52184101.tar.xz | |
meta-ampere: mtmitchell: correct checking PGOOD
Currently, in the platform initialization phase, BMC is checking PGOOD
gpio via both dbus and "/sys/class/gpio" methods. The "power_control"
application is polling PGOOD. Sometimes, "power_control" stops checking
the PGOOD's status due to a conflict with platform initialization. It
makes BMC can not control the power.
This commit removes the conflict between the "power_control" and the
platform initialization as below:
- Update ampere-platform-init.service to request the platform
initialization run before the "power_control".
- Update mtmitchell_platform_gpios_init.sh to remove checking PGOOD via
dbus.
Tested:
The platform initialization runs before the "power_control".
Turn on/off the host, reboot BMC, AC power work correctly.
Signed-off-by: Thang Tran <thuutran@amperecomputing.com>
Change-Id: Ic9619f93b8a49c578a8a0d733872a636ec6fc100
Diffstat (limited to 'meta-openembedded/meta-python/recipes-devtools/python/python3-process-tests_2.1.2.bb')
0 files changed, 0 insertions, 0 deletions