firmware: tie in call to data handler's open
A data handler can implement an open/close that is called during those
actions on the larger blob_id element. This is meant to allow a
possible configure step for a driver on the BMC-side.
Change-Id: I62efa762d2efb8b2140b9856819554fbf577405a
Signed-off-by: Patrick Venture <venture@google.com>
diff --git a/test/firmware_write_unittest.cpp b/test/firmware_write_unittest.cpp
index 58cb5b2..0ba20f5 100644
--- a/test/firmware_write_unittest.cpp
+++ b/test/firmware_write_unittest.cpp
@@ -59,6 +59,7 @@
auto handler = FirmwareBlobHandler::CreateFirmwareBlobHandler(blobs, data);
+ EXPECT_CALL(dataMock, open()).WillOnce(Return(true));
EXPECT_CALL(imageMock2, open("asdf")).WillOnce(Return(true));
EXPECT_TRUE(handler->open(
@@ -97,6 +98,7 @@
auto handler = FirmwareBlobHandler::CreateFirmwareBlobHandler(blobs, data);
+ EXPECT_CALL(dataMock, open()).WillOnce(Return(true));
EXPECT_CALL(imageMock2, open("asdf")).WillOnce(Return(true));
EXPECT_TRUE(handler->open(