Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-gpio-monitor / ca2637e69b69e174dbb0c82cad1ba6e973a2ba22
commitca2637e69b69e174dbb0c82cad1ba6e973a2ba22[log] [tgz]
authorBrandon Wyman <bjwyman@gmail.com>Thu Mar 04 12:41:21 2021 -0600
committerBrandon Wyman <bjwyman@gmail.com>Fri Mar 12 14:57:02 2021 -0600
tree05df9992eb75af890e22122cc601368a6d2ca607
parent3ce88a7b5a1c17ca53b63859a5dad840a995f42e [diff]
Fix SDK build issue due to updated arm-sdk

After a recent change to enable security flags:
d47f9a099a4ef992351237b0f2f562b5dc843397
compilation of the code in this repository with the arm-sdk results in
error messages from FORTIFY_SOURCE, which only compiles with
optimization levels 1 and 2.

Change the default build type to debugoptimized.

Reference changes:
    I910256c3aeffcbab0cbc33ced541b90576ce4151
    Ic1a91e58253fed283f67c44989fbc9126e18b7fe

Tested:
    SDK build with arm-sdk passes.
    Bitbake build passes.

Signed-off-by: Brandon Wyman <bjwyman@gmail.com>
Change-Id: I7eb1cdd23a8b4d8674de7d403b41114a44b8984c
1 file changed
tree: 05df9992eb75af890e22122cc601368a6d2ca607
  1. gpio-util/
  2. presence/
  3. test/
  4. .clang-format
  5. .gitignore
  6. 99-gpio-keys.rules
  7. argument.cpp
  8. argument.hpp
  9. evdev.cpp
  10. evdev.hpp
  11. file.hpp
  12. gpioMon.cpp
  13. gpioMon.hpp
  14. gpioMonMain.cpp
  15. LICENSE
  16. mainapp.cpp
  17. MAINTAINERS
  18. meson.build
  19. meson_options.txt
  20. monitor.cpp
  21. monitor.hpp
  22. phosphor-gpio-monitor@.service
  23. phosphor-gpio-presence@.service
  24. phosphor-multi-gpio-monitor.json
  25. phosphor-multi-gpio-monitor.service
  26. 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" } ]