| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
Run the obmc-chassis-reset@.target:
- Check if pgood is on
- If it is, create the file in /run/openbmc/chassis@%i-on and
- Run the systemctl command to start the chassis power on target
Resolves openbmc/openbmc#1094
Change-Id: I93f94fc1b75e35fd353387d0bed5569e07615171
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
|
|
|
|
|
|
|
|
|
| |
Once enabled these targets and services will be run after
a BMC reboot to check if pgood is on and if so, to create
a file which will be used by other power on services
to know whether they need to run or not.
Change-Id: Id2e75f9bce20f362d2f57a79e91ece1eaf7d7c45
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is the first commit in a series that will ensure
we do not run the chassis power on services when the
chassis is already on.
Specifically this is to handle the situation where the
chassis is on and the BMC is rebooted.
Change-Id: I733ca076f044731a4ba327fe2f46302dce5f4edd
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
|
|
|
|
|
|
|
| |
oneshot will cause the target to fail, which is
what we want on service failures
Change-Id: I1c3fe7159af51e92a2d0f4a7361e5e828675515d
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
|
|
|
|
| |
Change-Id: I5e4a0da68bfcebb12f3ac4161e63c145f9f73b0a
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
|
Given that these are already in the recipes-phosphor
directory this seemed redundant.
Change-Id: I48a1ab79e0eda88fc5e6af88f198ca3941e829b8
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|