openbmc/phosphor-gpio-monitor/README.md

5 ### `phosphor-gpio-monitor`
8 take action if requested. This implementation uses GPIO keys and only supports
12 ### `phosphor-multi-gpio-monitor`
14 This daemon accepts command line parameter as a well-defined GPIO configuration
16 defined in config based on gpio state change. It uses libgpiod library.
20 New implementation (phosphor-multi-gpio-monitor) provides multiple gpio line
21 monitoring in single instance of phosphor-multi-gpio-monitor running. It is very
23 line by name defined in kernel.
27 There is a phosphor-multi-gpio-monitor.json file that defines details of GPIOs
34 2. LineName: this is the line name defined in device tree for specific gpio
35 3. GpioNum: GPIO offset, this field is optional if LineName is defined.
37    ("gpiochip0"). This field is not required if LineName is defined.
47    INIT_LOW will be called (if defined).
48 8. Continue: This is a optional flag and if it is defined as true then this gpio
49    will be monitored continuously. If not defined then monitoring of this gpio
79 ### `phosphor-multi-gpio-presence`
81 This daemon accepts command line parameter as a well-defined GPIO configuration
83 presence as defined in config based on gpio state change. It uses libgpiod
88 New implementation (phosphor-multi-gpio-presence) provides multiple gpio line
89 monitoring in single instance of phosphor-multi-gpio-presence running. It is
91 GPIO line by name defined in kernel.
95 There is a phosphor-multi-gpio-presence.json file that defines details of GPIOs
102 2. LineName: this is the line name defined in device tree for specific gpio
103 3. GpioNum: GPIO offset, this field is optional if LineName is defined.
105    ("gpiochip0"). This field is not required if LineName is defined.