path: root/mboxd_msg.h
diff options
authorSuraj Jitindar Singh <>2017-04-27 11:55:26 +1000
committerSuraj Jitindar Singh <>2017-05-03 17:19:15 +1000
commit5a3a0664b63feba8aff288a5691a9f873e4ea6eb (patch)
tree7e09d96625c0e7b6e48e5874481eca7627fd99bc /mboxd_msg.h
parent6479ed4034747414068d2c328f58b51eed737a24 (diff)
mboxd: Implement timeout return value in GET_MBOX_INFO
The previous patch added a new return field in GET_MBOX_INFO called "suggested timeout" to be used to provide a suggested maximum timeout value to the host. Add this to the return arguments of GET_MBOX_INFO. Note that the host is free to ignore the value and the daemon can leave this blank if it doesn't want to provide a timeout. We hard code a milliseconds per megabyte value which was determined to be approximately 8000 based on testing and is close to linear as the access size changes. Testing was conducted on an Aspeed ast2500 on a Witherspoon with the dev-4.7 OpenBMC branch. Signed-off-by: Suraj Jitindar Singh <> Change-Id: If24e41ebb1d9f03c2bdcca84819f9430fd3eeff6
Diffstat (limited to 'mboxd_msg.h')
1 files changed, 7 insertions, 2 deletions
diff --git a/mboxd_msg.h b/mboxd_msg.h
index 44a2f91..7d81d7a 100644
--- a/mboxd_msg.h
+++ b/mboxd_msg.h
@@ -18,8 +18,13 @@
#ifndef MBOXD_MSG_H
#define MBOXD_MSG_H
-#define NO_BMC_EVENT false
-#define SET_BMC_EVENT true
+#include "common.h"
+/* Estimate as to how long (milliseconds) it takes to access a MB from flash */
+#define FLASH_ACCESS_MS_PER_MB 8000
+#define NO_BMC_EVENT false
+#define SET_BMC_EVENT true
struct mbox_msg {
uint8_t command;
OpenPOWER on IntegriCloud