dbus-sensors: Assert on fault led group if cable is not properly connected
Signed-off-by: Chu Lin <linchuyuan@google.com>
Change-Id: I56b5bf1731b7afba9d6e99f91a20abe2d1502383
diff --git a/designs/gpio-based-cable-presence.md b/designs/gpio-based-cable-presence.md
index 1ed1cad..8c4987c 100644
--- a/designs/gpio-based-cable-presence.md
+++ b/designs/gpio-based-cable-presence.md
@@ -35,13 +35,19 @@
"Name": "cable0",
"GpioLine": "osfp0",
"Polarity": "active_low",
- "Type": "GPIOCableSensing"
+ "Type": "GPIOCableSensing",
+ "FaultLedGroup": [
+ "attention"
+ ]
},
{
"Name": "cable1",
"GpioLine": "osfp1",
"Polarity": "active_high",
- "Type": "GPIOCableSensing"
+ "Type": "GPIOCableSensing",
+ "FaultLedGroup": [
+ "attention"
+ ]
}
]
}
@@ -51,7 +57,10 @@
should tell the daemon whether it needs to revert the GPIO signal. Each entry
from the config would get translated into one object on the dbus. In addition,
the daemon polls the gpio presence signal for these objects in an interval of
-10 seconds.
+10 seconds. When the cable is not properly seated, the daemon will assert on
+the corresponding fault led group. This should cause the corresponding led to
+blink or to turn on base on how phosphor-led-manager is configured. No action
+is taken if FaultLedGroup is empty.
On the IPMI sIDe, the presence states will be grouped into fewer SDR IDs in
order to save SDR IDs for ipmi. Given the following example,