Mechanism to associate sensor/effecter to FRU entity
The "entity_path" key is defined in PDR JSONs and will have an FRU D-Bus object
path as the value, if this is present, the entity type, instance, and container
id should be associate with the FRU entity.
Tested: test JSON with https://gist.github.com/lxwinspur/7225a9301ccfcbff1f6549203405b4fa
after executing the following command, get the entity information from FruHandler
entity_type = 120
entity_instance_num = 1
entity_container_id = 0
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: I019f9a0b9d4dbec20a71dfd797f30ac8f57f67b8
diff --git a/test/pdr_jsons/state_effecter/malformed/effecter_pdr.json b/test/pdr_jsons/state_effecter/malformed/effecter_pdr.json
index d6b0213..826e27a 100644
--- a/test/pdr_jsons/state_effecter/malformed/effecter_pdr.json
+++ b/test/pdr_jsons/state_effecter/malformed/effecter_pdr.json
@@ -4,6 +4,7 @@
"pdrType": 11,
"entries": [
{
+ "entity_path": "/xyz/openbmc_project/foo",
"type": 33
"instance": 0,
"container": 0,
@@ -49,6 +50,7 @@
]
},
{
+ "entity_path": "/xyz/openbmc_project/foo",
"type": 100,
"instance": 0,
"container": 0,
@@ -103,6 +105,10 @@
"pdrType": 9,
"entries": [
{
+ "entity_path": "/xyz/openbmc_project/foo",
+ "type": 0,
+ "instance": 0,
+ "container": 0,
"base_unit": 21,
"rate_unit": 3,
"effecter_resolution_init": 1,