commit 3efcf37b33a73fbf0662a9b148a5fbdca2f81dce
author Andrei Kartashev <a.kartashev@yadro.com> Wed Dec 29 15:32:17 2021 +0300
committer Andrei Kartashev <a.kartashev@yadro.com> Sat Jan 15 07:50:11 2022 +0000
tree cb45a6da49284120c2897d008e2ec9b80d461c34
parent 50fe8ee363251f4a573f811fda88d3cb90122b89

use same consumer for each gpio request

The `consumer` field of line_request supposed to represent consumer
application. Currently x86-power-control uses different names for
different cases: application name for inputs and function name for
outputs.

There is no benefits in use function name as consumer, so use
application name in both cases.

Tested: gpioinfo | grep -i power-control
        see all gpios, used by x86-power-control
Signed-off-by: Andrei Kartashev <a.kartashev@yadro.com>
Change-Id: I1baef7bd4bb9b0c2efcb423f513f56d244a0cbdd

src/power_control.cpp

diff --git a/src/power_control.cpp b/src/power_control.cpp
index b99556a..84160bd 100644
--- a/src/power_control.cpp
+++ b/src/power_control.cpp
@@ -39,6 +39,7 @@
 PersistentState appState;
 
 static std::string node = "0";
+static const std::string appName = "power-control";
 
 enum class DbusConfigType
 {
@@ -1134,8 +1135,7 @@
 
     try
     {
-        gpioLine.request(
-            {"power-control", gpiod::line_request::EVENT_BOTH_EDGES, {}});
+        gpioLine.request({appName, gpiod::line_request::EVENT_BOTH_EDGES, {}});
     }
     catch (const std::exception& e)
     {
@@ -1171,8 +1171,8 @@
     // Request GPIO output to specified value
     try
     {
-        gpioLine.request(
-            {__FUNCTION__, gpiod::line_request::DIRECTION_OUTPUT, {}}, value);
+        gpioLine.request({appName, gpiod::line_request::DIRECTION_OUTPUT, {}},
+                         value);
     }
     catch (const std::exception& e)
     {