phosphor: ensure host state sensors cleared on host quiesce

By design, nothing occurs in the obmc-host-quiesce target. The point is
to leave everything in its current state so external debug can occur.
The host states sensors should be reset though so other BMC software
knows the host is in an undefined state.

Tested:
- Verified sensors were reset when obmc-host-quiesce target was started

Change-Id: Ice56ee74a706d752d291cff56846d2c994cf7a4f
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
1 file changed
tree: ab9970ca355c7d0d5c60320dc0f10bdc9b35bde8
  1. aspeed-layer/
  2. classes/
  3. conf/
  4. nuvoton-layer/
  5. raspberrypi/
  6. recipes-connectivity/
  7. recipes-core/
  8. recipes-devtools/
  9. recipes-extended/
  10. recipes-graphics/
  11. recipes-phosphor/
  12. recipes-protocols/
  13. recipes-support/
  14. recipes-textproc/
  15. recipes-x86/
  16. COPYING.apache-2.0
  17. COPYING.MIT
  18. LICENSE
  19. MAINTAINERS
  20. README.md
  21. recipes.txt
README.md

OpenBMC

meta-phosphor is the OpenBMC layer. This layer should be included for all OpenBMC systems. The OpenBMC layer contains content which is shared between all OpenBMC systems.