|
@@ -11,7 +11,7 @@
|
|
|
#define FW_DYNAMIC_INFO_MAGIC_VALUE 0x4942534f
|
|
|
|
|
|
/** Maximum supported info version */
|
|
|
-#define FW_DYNAMIC_INFO_VERSION 0x1
|
|
|
+#define FW_DYNAMIC_INFO_VERSION 0x2
|
|
|
|
|
|
/** Possible next mode values */
|
|
|
#define FW_DYNAMIC_INFO_NEXT_MODE_U 0x0
|
|
@@ -35,6 +35,22 @@ struct fw_dynamic_info {
|
|
|
unsigned long next_mode;
|
|
|
/** Options for OpenSBI library */
|
|
|
unsigned long options;
|
|
|
+ /**
|
|
|
+ * Preferred boot HART id
|
|
|
+ *
|
|
|
+ * It is possible that the previous booting stage uses same link
|
|
|
+ * address as the FW_DYNAMIC firmware. In this case, the relocation
|
|
|
+ * lottery mechanism can potentially overwrite the previous booting
|
|
|
+ * stage while other HARTs are still running in the previous booting
|
|
|
+ * stage leading to boot-time crash. To avoid this boot-time crash,
|
|
|
+ * the previous booting stage can specify last HART that will jump
|
|
|
+ * to the FW_DYNAMIC firmware as the preferred boot HART.
|
|
|
+ *
|
|
|
+ * To avoid specifying a preferred boot HART, the previous booting
|
|
|
+ * stage can set it to -1UL which will force the FW_DYNAMIC firmware
|
|
|
+ * to use the relocation lottery mechanism.
|
|
|
+ */
|
|
|
+ unsigned long boot_hart;
|
|
|
} __packed;
|
|
|
|
|
|
#endif
|