designs/inventory/gpio-based-hardware-inventory.md

130 participant EM
137 activate EM
138 EM ->> EM: PROBE true on <br> xyz.openbmc_project.FruDevice <br> PRODUCT_PRODUCT_NAME=Yosemite V4
139 EM ->> PresenceDaemon: expose Configuration <br> xyz.openbmc_project.Configuration.GPIODeviceDetect…
140 deactivate EM
147 PresenceDaemon ->> EM: expose <br>xyz.openbmc_project.Inventory.Source.DevicePresence <br> Name=com…
148 activate EM
150 EM ->> EM: PROBE true on <br>xyz.openbmc_project.Inventory.Source.DevicePresence <br> Name=com.meta…
151 EM ->> AnyService: expose new Configuration <br> Example: Voltage Sensor
152 deactivate EM
163 PresenceDaemon ->> EM: remove <br>xyz.openbmc_project.Inventory.Source.DevicePresence <br> Name=com…
166 activate EM
167 EM ->> EM: PROBE false on <br>xyz.openbmc_project.Inventory.Source.DevicePresence <br> Name=com.met…
168 EM ->> AnyService: remove new Configuration <br> Example: Voltage Sensor
169 deactivate EM
176 - EM exposes configuration for 'gpio-presence-sensor'
181 - EM can probe new configuration files based on that dbus interface, via PROBE
183 - EM exposes the new configuration for the detected hardware
189 - EM detects that via dbus matcher
190 - EM removes the configuration for that hardware from dbus
194 - EM exposes configuration for 'gpio-presence-sensor'
199 - EM removes the config for 'gpio-presence-sensor'
202 - EM detects that via dbus matcher
203 - EM removes the configuration for that hardware from dbus
233       Choosing 'uint64' instead of 'bool' here for compatibility with how EM
269 #### Proposed EM Configuration Schema
303 ### Example EM Config Fragments
392   presence daemon, and it's an explicit non-goal of EM to implement any presence
393   detection. Maintainers have confirmed that EM should not implement this
396 - Another daemon which would expose inventory items based on EM configuration.
397   This would mean EM does not need to expose the item-specific inventory
401   means EM would lose any semantic knowledge of the entities it exposes and