| commit | 65c0101c017e725c1470d60e1fd054795c5c6a23 | [log] [tgz] |
|---|---|---|
| author | Andrew Geissler <geissonator@yahoo.com> | Tue Jun 15 14:03:34 2021 -0500 |
| committer | Andrew Geissler <geissonator@yahoo.com> | Wed Jun 30 14:46:53 2021 -0500 |
| tree | 0d10929f1dd4edc9cfec1d17118614b74f71d48d | |
| parent | 5c3f9258c930276e170708644093944854c3fdb7 [diff] |
bmc-reset: check if host is running This is the backup plan to ensuring the host is not running before the BMC issues a power off to the system. Prior to this procedure being called, the BMC has tried all other communication mechanisms to talk with the host and they have failed. The design is that the host firmware will write the value 0xA5000001 to Mailbox scratch register 12 when they are up and running to a point where communication to the BMC is no longer required to function. On a power off or shutdown this register is cleared by the host and BMC firmware. If the BMC sees the 0xA5000001 pattern in the scratch register then it assumes the host is running and will leave power on to the system. Why not put this in phosphor-state-manager where the other checks are for the host running? - This is a very POWER10 specific piece of logic - A lot of tight coupling would have been required between state-manager and proc-control - In the end, it was less work to just put this in proc-control Tested: - Verified when CFAM is not A5000001, call returns without error and /run file is not created - Verified when CFAM is A5000001, call returns without error and /run file is created Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I3f6be9160d8d89e556a722d9f6cb00f94be2b994
Contains procedures that interact with the OpenPower nest chipset.
To build this package, do the following steps:
1. ./bootstrap.sh
2. ./configure ${CONFIGURE_FLAGS}
3. make
To build with phal feature:
1. ./bootstrap.sh
2. ./configure ${CONFIGURE_FLAGS} --enable-phal --enable-openfsi
3. make
To clean the repository run `./bootstrap.sh clean`.