Don't try to read GPIOs when no device path

For certain PGOOD faults, the code may try to read a GPIO off of an IO
expander to further isolate the error.  If there was a problem with the
device driver detecting that IO expander, then the code was running down
a path where it would still try to read that IO expander, but using an
empty device path which would just generate extra error traces in the
journal.  Avoid this by checking for this empty path and then not
reading those GPIOs.

Change-Id: I40a3e0c13e392fa58d87f53c8911eb96c9cd7f2c
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
1 file changed
tree: 8568a90b89c8a8d7319227ec72ea0000b1534287
  1. org/
  2. power-sequencer/
  3. power-supply/
  4. test/
  5. .clang-format
  6. .gitignore
  7. argument.hpp
  8. bootstrap.sh
  9. configure.ac
  10. device.hpp
  11. device_monitor.hpp
  12. elog-errors.hpp
  13. file.hpp
  14. gpio.cpp
  15. gpio.hpp
  16. LICENSE
  17. MAINTAINERS
  18. Makefile.am
  19. names_values.hpp
  20. pmbus.cpp
  21. pmbus.hpp
  22. README.md
  23. utility.cpp
  24. utility.hpp
README.md

Code for detecting and analyzing power faults on Witherspoon.

To Build

To build this package, do the following steps:

    1. ./bootstrap.sh
    2. ./configure ${CONFIGURE_FLAGS}
    3. make

To full clean the repository again run `./bootstrap.sh clean`.