Providing infra for FRUs which are accessible through host but host is
not sending the details for those FRUs
- This commit adds a hand written YAML file that specifies IPMI FRU
information. It is for special case where FRU info is not coming as a
write-fru, it coming as a write-sensor from host because host doesn't
have the required i2c access to read the GPU FRU data.
- The YAML in this commit is mostly empty, and system specific overrides
are supposed to add appropriate content.
Partially Resolves openbmc/openbmc#3039
Change-Id: I20b43d1bb4c472dc590d254b72340fb19c52b811
Signed-off-by: Nagaraju Goruganti <ngorugan@in.ibm.com>
diff --git a/meta-phosphor/common/recipes-phosphor/ipmi/phosphor-ipmi-fru-read-not-sent-by-host-inventory/fru-config-not-sent-by-host.yaml b/meta-phosphor/common/recipes-phosphor/ipmi/phosphor-ipmi-fru-read-not-sent-by-host-inventory/fru-config-not-sent-by-host.yaml
new file mode 100644
index 0000000..9fa1fed
--- /dev/null
+++ b/meta-phosphor/common/recipes-phosphor/ipmi/phosphor-ipmi-fru-read-not-sent-by-host-inventory/fru-config-not-sent-by-host.yaml
@@ -0,0 +1,21 @@
+# A YAML similar to this sample would have to be generated, for eg with MRW
+# inputs and system configuration, to depict IPMI FRU information.
+#
+# This file maps phosphor dbus inventory properties to IPMI properties
+#
+# This YAML could help generate C++ code.
+# Format of the YAML:
+# Fruid:
+# Associated Fru paths
+# d-bus Interfaces
+# d-bus Properties
+# IPMI Fru mapping
+#20:
+# /system/chassis/motherboard/gv100card0:
+# entityID: 3
+# entityInstance: 1
+# interfaces:
+# xyz.openbmc_project.Inventory.Item:
+# PrettyName:
+# IPMIFruProperty: Board Name
+# IPMIFruSection: Board