* [PATCH v1] Documentation: efi: provide watchdog documentation
@ 2019-02-08 7:28 Oleksij Rempel
0 siblings, 0 replies; only message in thread
From: Oleksij Rempel @ 2019-02-08 7:28 UTC (permalink / raw)
To: barebox; +Cc: Oleksij Rempel
Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
---
Documentation/boards/efi.rst | 30 ++++++++++++++++++++++++++++++
1 file changed, 30 insertions(+)
diff --git a/Documentation/boards/efi.rst b/Documentation/boards/efi.rst
index f59bb1d5ba..a3241b6ed9 100644
--- a/Documentation/boards/efi.rst
+++ b/Documentation/boards/efi.rst
@@ -327,3 +327,33 @@ compile EDK2.
mov %fs, %rax
pushq %rax
+(U)EFI Watchdog
+---------------
+
+(U)EFI provides basic watchdog support. Depending on the system implementation
+it can be a software or hardware watchdog. Within the (U)EFI specification it
+is described as following:
+"If the watchdog timer expires, the event is logged by the firmware. The system
+may then either reset with the Runtime Service ResetSystem(), or perform a
+platform specific action that must eventually cause the platform to be reset.
+The watchdog timer is armed before the firmware's boot manager invokes an EFI
+boot option. The watchdog must be set to a period of 5 minutes. The EFI Image
+may reset or disable the watchdog timer as needed. If control is returned to
+the firmware's boot manager, the watchdog timer must be disabled. The watchdog
+timer is only used during boot services. On successful completion of
+ExitBootServices() the watchdog timer is disabled." See page 186:
+https://uefi.org/sites/default/files/resources/UEFI_Spec_2_1_D.pdf
+
+Current linux kernel (v5.0) will execute ExitBootServices() during the early
+boot stage and thus will automatically disable the (U)EFI watchdog. Since it is
+a proper behavior according to the (U)EFI specification, it is impossible to
+protect full boot chain by using this watchdog. It is recommended to use
+alternative hardware watchdog, preferably started before bootloader. If (U)EFI
+firmware lacks this feature, bootloader should be able to start an alternative
+hardware watchdog on its own. Before implementing this kind of workaround
+please make sure (U)EFI watchdog is not using the same hardware as alternative
+watchdog.
+
+Nevertheless, barebox is providing access to the (U)EFI SetWatchdogTimer()
+interface over internal watchdog framework.
+
--
2.20.1
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2019-02-08 7:28 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-02-08 7:28 [PATCH v1] Documentation: efi: provide watchdog documentation Oleksij Rempel
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox