docs/designs/entity-manager-hw-id-vpd-discover-via-device-tree.md

1 # Entity-Manager HW ID: VPD Discovery via Device-Tree Properties
13 Entity-Manager's 'fru-device' daemon that most platforms rely on.
16 gathered from device tree file paths for Entity-Manager consumption.
23 [As described in Entity-Manager documentation](https://github.com/openbmc/entity-manager/blob/maste…
26 by Entity-Manager's fru-device daemon. The current FRU-device daemon is able to
37 Once VPD is made available on D-Bus, it can be referenced by the Entity-Manager
97 way for Entity-Manager to reference it during the probe evaluations used in
99 being made available on D-Bus will be enough to enable basic Entity-Manager
110 Entity-Manager to enable BMC detection and handling of HPE Gen 11 hardware (and
121 - Vital product data properties should be referenced in Entity-Manager config
141 - Entity-Manager probes that reference properties from the
148 ### Entity-Manager probes are extended to handle reading data from arbitrary device-tree nodes
223 ### Service is hosted in Entity-Manager [ACCEPTED after TOF re-examination]
231 1. Community doesn't want to host VPD -> DBus daemons in Entity-Manager repo
234 would be better to host this device-tree VPD daemon in Entity-Manager alongside
334 rely on this service for Entity-Manager HW/config detection.
341 have the device-tree VPD parser daemon hosted in the Entity-Manager repo
347 daemon will be hosted in Entity-Manager alongside the existing FRU-device VPD
350 Entity-Manager will also have configuration files added for HPE hardware that
362 Practically, the whole of the service stack (including Entity-Manager probe
364 an Entity-Manager config's probe to trigger on match with a known HPE-HW