summaryrefslogtreecommitdiffstats
path: root/meta-phosphor/common/recipes-phosphor/chassis/obmc-fsi-scan
Commit message (Collapse)AuthorAgeFilesLines
* Add FSI enable/disable services for cronus useMatt Spinler2017-03-161-16/+0
| | | | | | | | | | | Start fsi-disable.service to unbind the FSI Driver. Start fsi-enable.service to bind it again and rescan. Also added a fsi-bind@.service so we can ensure the driver is bound each power on. Change-Id: I5fa62b44994aea3bb645e755187f29e720bf3bce Signed-off-by: Matt Spinler <spinler@us.ibm.com>
* Do not run chassis power target services if power onAndrew Geissler2017-03-151-0/+1
| | | | | | | | | | | | 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>
* Ensure FSI scan runs before services that use FSIMatt Spinler2017-03-011-0/+2
| | | | | | | | The FSI scan must be done before start_host and vcs_workaround run in order for them to work propertly. Change-Id: I1305a65763ba35721d5655f1f3e6c2d8af5fdc71 Signed-off-by: Matt Spinler <spinler@us.ibm.com>
* Add service to trigger OpenFSI driver to do a scanMatt Spinler2017-02-241-0/+13
After PGOOD comes up, the FSI driver needs to do a scan to find the FSI devices. Change-Id: I1b4eeec191408a36b37d9044279bdf067deb2b15 Signed-off-by: Matt Spinler <spinler@us.ibm.com>
OpenPOWER on IntegriCloud