Removed the force init option from initialize()
The ability to keep track of all objects that are specific to a given
chip type is more complicated than what it is worth to support the
ability to reinitialize a single chip type. Instead, the user
application will need to uninitialize and reinitialize all needed
chip types.
In addition, the user application must ensure it does not try to
initialize the same chip type more than once to prevent memory bloat.
Change-Id: I8b33012553fe1bea75cdd319c53e7bd5bff91726
Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
diff --git a/src/isolator/hei_isolator.cpp b/src/isolator/hei_isolator.cpp
index d932659..41d33a9 100644
--- a/src/isolator/hei_isolator.cpp
+++ b/src/isolator/hei_isolator.cpp
@@ -13,14 +13,11 @@
namespace libhei
{
-ReturnCode Isolator::initialize(void* i_buffer, size_t i_bufferSize,
- bool i_forceInit)
+void Isolator::initialize(void* i_buffer, size_t i_bufferSize)
{
- ReturnCode rc;
-
// BEGIN temporary code
- HEI_INF("Isolator::initialize(%p,%" PRIu64 ",%d)", i_buffer,
- (uint64_t)i_bufferSize, i_forceInit);
+ HEI_INF("Isolator::initialize(%p,%" PRIu64 ")", i_buffer,
+ (uint64_t)i_bufferSize);
auto& scom_fw = Flyweight<ScomRegister>::getSingleton();
auto& idScom_fw = Flyweight<IdScomRegister>::getSingleton();
@@ -45,8 +42,6 @@
iv_isoStart[static_cast<ChipType_t>(0xdeadbeef)].push_back(
{&node0, ATTN_TYPE_CHECKSTOP});
// END temporary code
-
- return rc;
}
void Isolator::uninitialize()