Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-gpio-monitor / d34bd96c262cd326583acba76a651426f24a35ae
commitd34bd96c262cd326583acba76a651426f24a35ae[log] [tgz]
authorVijay Khemka <vijaykhemka@fb.com>Tue Oct 29 12:28:07 2019 -0700
committerBrad Bishop <bradleyb@fuzziesquirrel.com>Mon Nov 04 16:48:18 2019 +0000
treefdf50330a1d4a18a0c41184b3845c919e8dabb06
parent939a6431661931b3d31c46ec0310c553e22308d1 [diff]
Add systemd units for new phosphor-multi-gpio-monitor

Also added sample phosphor-multi-gpio-monitor.json for
configuration of list of GPIO to be monitored. Platform
specific file can be added through bbappend file.

Signed-off-by: Vijay Khemka <vijaykhemka@fb.com>
Change-Id: I3a2fac155be4583aeee52f018da6be0b506633fd
3 files changed
tree: fdf50330a1d4a18a0c41184b3845c919e8dabb06
  1. gpio-util/
  2. presence/
  3. test/
  4. .clang-format
  5. .gitignore
  6. argument.cpp
  7. argument.hpp
  8. evdev.cpp
  9. evdev.hpp
  10. file.hpp
  11. gpioMon.cpp
  12. gpioMon.hpp
  13. gpioMonMain.cpp
  14. LICENSE
  15. mainapp.cpp
  16. MAINTAINERS
  17. meson.build
  18. meson_options.txt
  19. monitor.cpp
  20. monitor.hpp
  21. phosphor-gpio-monitor@.service
  22. phosphor-gpio-presence@.service
  23. phosphor-multi-gpio-monitor.json
  24. phosphor-multi-gpio-monitor.service
  25. README.md
README.md

phosphor-gpio-monitor

This daemon accepts a command line parameter for monitoring single gpio line and take action if requested. This implementation uses GPIO keys and only supports monitoring single GPIO line, for multiple lines, user has to run this daemon seperately for each gpio line.

phosphor-multi-gpio-monitor

This daemon accepts command line parameter as a well-defined GPIO configuration file in json format to monitor list of gpios from config file and take action defined in config based on gpio state change. It uses libgpiod library.

Difference

New implementation (phosphor-multi-gpio-monitor) provides multiple gpio line monitoring in single instance of phosphor-multi-gpio-monitor running. It is very easy to add list of gpios into JSON config file and it also supports of GPIO line by name defined in kernel.

Configuration

There is a phosphor-multi-gpio-monitor.json file that defines details of GPIOs which is required to be monitored. This file can be replaced with a platform specific configuration file via bbappend.

Following are fields in json file

  1. Name: Name of gpio for reference.
  2. LineName: this is the line name defined in device tree for specific gpio
  3. GpioNum: GPIO offset, this field is optional if LineName is defined.
  4. ChipId: This is device name either offset ("0") or complete gpio device ("gpiochip0"). This field is not required if LineName is defined.
  5. EventMon: Event of gpio to be monitored. This can be "FALLING", "RISING" OR "BOTH". Default value for this is "BOTH".
  6. Target: This is an optional systemd service which will get started after triggering event. A journal entry will be added for every event occurs irrespective of this definition.
  7. Continue: This is a optional flag and if it is defined as true then this gpio will be monitored continously. If not defined then monitoring of this gpio will stop after first event.

Sample config file

[ { "Name": "PowerButton", "LineName": "POWER_BUTTON", "GpioNum": 34, "ChipId": "gpiochip0", "EventMon": "BOTH", "Continue": true }, { "Name": "PowerGood", "LineName": "PS_PWROK", "EventMon": "FALLING", "Continue": false }, { "Name": "SystemReset", "GpioNum": 46, "ChipId": "0" } ]