Searched hist:a66ac0fc4d65f71b37fdabaef1616dac3241c4cc (Results 1 – 4 of 4) sorted by relevance
/openbmc/phosphor-gpio-monitor/ |
H A D | gpioMon.hpp | diff a66ac0fc4d65f71b37fdabaef1616dac3241c4cc Mon Jan 09 03:12:23 CST 2023 Delphine CC Chiu <Delphine_CC_Chiu@wiwynn.com> Support event multi targets
Description: - Support event multi targets.
Design: - The origin multi-gpio-monitor doesn't detect the comming events are rising or falling and it can only start one service after events triggered.
- We need to do corresponding actions when gpio pin rising or falling. So we modify multi-gpio-monitor config json and read the rising actions and falling actions in it.
- When service monitored one gpio status is changed, service will detect that it is a rising or falling event and then call systemd startUnit to start services that set in config json.
- For example with config json below: When PowerGood is falling, "PowerGoodFalling.service" and "PowerOff.service" will start. [ { "Name": "PowerGood", "ChipId": "0", "GpioNum": 14, "EventMon": "BOTH", "Targets": { "FALLING": ["PowerGoodFalling.service", "PowerOff.service"], "RISING": ["PowerGoodRising.service", "PowerOn.service"] }, "Continue": true } ]
Test Case: Check that corresponding targets start or not - pass
Signed-off-by: Delphine CC Chiu <Delphine_CC_Chiu@wiwynn.com> Change-Id: I043d4385b91a04d360a4d50048320db15e63ac74
|
H A D | README.md | diff a66ac0fc4d65f71b37fdabaef1616dac3241c4cc Mon Jan 09 03:12:23 CST 2023 Delphine CC Chiu <Delphine_CC_Chiu@wiwynn.com> Support event multi targets
Description: - Support event multi targets.
Design: - The origin multi-gpio-monitor doesn't detect the comming events are rising or falling and it can only start one service after events triggered.
- We need to do corresponding actions when gpio pin rising or falling. So we modify multi-gpio-monitor config json and read the rising actions and falling actions in it.
- When service monitored one gpio status is changed, service will detect that it is a rising or falling event and then call systemd startUnit to start services that set in config json.
- For example with config json below: When PowerGood is falling, "PowerGoodFalling.service" and "PowerOff.service" will start. [ { "Name": "PowerGood", "ChipId": "0", "GpioNum": 14, "EventMon": "BOTH", "Targets": { "FALLING": ["PowerGoodFalling.service", "PowerOff.service"], "RISING": ["PowerGoodRising.service", "PowerOn.service"] }, "Continue": true } ]
Test Case: Check that corresponding targets start or not - pass
Signed-off-by: Delphine CC Chiu <Delphine_CC_Chiu@wiwynn.com> Change-Id: I043d4385b91a04d360a4d50048320db15e63ac74
|
H A D | gpioMon.cpp | diff a66ac0fc4d65f71b37fdabaef1616dac3241c4cc Mon Jan 09 03:12:23 CST 2023 Delphine CC Chiu <Delphine_CC_Chiu@wiwynn.com> Support event multi targets
Description: - Support event multi targets.
Design: - The origin multi-gpio-monitor doesn't detect the comming events are rising or falling and it can only start one service after events triggered.
- We need to do corresponding actions when gpio pin rising or falling. So we modify multi-gpio-monitor config json and read the rising actions and falling actions in it.
- When service monitored one gpio status is changed, service will detect that it is a rising or falling event and then call systemd startUnit to start services that set in config json.
- For example with config json below: When PowerGood is falling, "PowerGoodFalling.service" and "PowerOff.service" will start. [ { "Name": "PowerGood", "ChipId": "0", "GpioNum": 14, "EventMon": "BOTH", "Targets": { "FALLING": ["PowerGoodFalling.service", "PowerOff.service"], "RISING": ["PowerGoodRising.service", "PowerOn.service"] }, "Continue": true } ]
Test Case: Check that corresponding targets start or not - pass
Signed-off-by: Delphine CC Chiu <Delphine_CC_Chiu@wiwynn.com> Change-Id: I043d4385b91a04d360a4d50048320db15e63ac74
|
H A D | gpioMonMain.cpp | diff a66ac0fc4d65f71b37fdabaef1616dac3241c4cc Mon Jan 09 03:12:23 CST 2023 Delphine CC Chiu <Delphine_CC_Chiu@wiwynn.com> Support event multi targets
Description: - Support event multi targets.
Design: - The origin multi-gpio-monitor doesn't detect the comming events are rising or falling and it can only start one service after events triggered.
- We need to do corresponding actions when gpio pin rising or falling. So we modify multi-gpio-monitor config json and read the rising actions and falling actions in it.
- When service monitored one gpio status is changed, service will detect that it is a rising or falling event and then call systemd startUnit to start services that set in config json.
- For example with config json below: When PowerGood is falling, "PowerGoodFalling.service" and "PowerOff.service" will start. [ { "Name": "PowerGood", "ChipId": "0", "GpioNum": 14, "EventMon": "BOTH", "Targets": { "FALLING": ["PowerGoodFalling.service", "PowerOff.service"], "RISING": ["PowerGoodRising.service", "PowerOn.service"] }, "Continue": true } ]
Test Case: Check that corresponding targets start or not - pass
Signed-off-by: Delphine CC Chiu <Delphine_CC_Chiu@wiwynn.com> Change-Id: I043d4385b91a04d360a4d50048320db15e63ac74
|