Remove FRU vs Module VPD Handling
Some keywords were arbitrarily chosen to serve as FRU VPD
for dual chip modules (DCM - same FRU with two VPD chips).
However, since we expose both chips in such FRUs as
unique inventory items as well as unique Redfish endpoints,
having one of them serve as the VPD for the entire FRU makes
little sense.
This commit gets rid of all the complexity added to handle
DCMs. There is no need for the "inheritEI" and "type" keys
in the inventory JSONs too.
Signed-off-by: Santosh Puranik <santosh.puranik@in.ibm.com>
Change-Id: Ia89a44f91daac01f53748409a7633612de8930d6
diff --git a/vpd-manager/editor_impl.hpp b/vpd-manager/editor_impl.hpp
index d9b0ff1..c03354a 100644
--- a/vpd-manager/editor_impl.hpp
+++ b/vpd-manager/editor_impl.hpp
@@ -208,26 +208,9 @@
// If requested Interface is common Interface
bool isCI;
-
- /** @brief This API will be used to find out Parent FRU of Module/CPU
- *
- * @param[in] - moduleObjPath, object path of that FRU
- * @param[in] - fruType, Type of Parent FRU
- * for Module/CPU Parent Type- FruAndModule
- *
- * @return returns vpd file path of Parent Fru of that Module
- */
- std::string getSysPathForThisFruType(const std::string& moduleObjPath,
- const std::string& fruType);
-
- /** @brief This API will search for correct EEPROM path for asked CPU
- * and will init vpdFilePath
- */
- void getVpdPathForCpu();
-
}; // class EditorImpl
} // namespace editor
} // namespace manager
} // namespace vpd
-} // namespace openpower
+} // namespace openpower
\ No newline at end of file