summaryrefslogtreecommitdiffstats
path: root/drivers/watchdog
diff options
context:
space:
mode:
authorAhmad Fatoum <a.fatoum@pengutronix.de>2019-10-23 18:55:58 +0200
committerSascha Hauer <s.hauer@pengutronix.de>2019-10-24 09:59:30 +0200
commit2731cc09db884b5089d027a412e0396d07d23f42 (patch)
tree7372f3c27f55ec8a8d5f11fb60af355121e47e30 /drivers/watchdog
parent60101d8efc8036853345061c288b4789be4c3132 (diff)
downloadbarebox-2731cc09db884b5089d027a412e0396d07d23f42.tar.gz
barebox-2731cc09db884b5089d027a412e0396d07d23f42.tar.xz
watchdog: efi: bump down priority below default
The barebox EFI documentation notes: > 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 the proper behavior according to the (U)EFI specification, it > is impossible to protect full boot chain by using this watchdog only. > It is recommended to use an alternative hardware watchdog Heed the advice and bump down the EFI watchdog priority below the watchdog priority default. This ensures the EFI watchdog isn't inadvertently used if other watchdogs are registered. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'drivers/watchdog')
-rw-r--r--drivers/watchdog/efi_wdt.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/watchdog/efi_wdt.c b/drivers/watchdog/efi_wdt.c
index 8e3e51b7a9..ea1ede1381 100644
--- a/drivers/watchdog/efi_wdt.c
+++ b/drivers/watchdog/efi_wdt.c
@@ -41,6 +41,7 @@ static int efi_wdt_probe(struct device_d *dev)
priv->wd.set_timeout = efi_wdt_set_timeout;
priv->wd.hwdev = dev;
priv->dev = dev;
+ priv->wd.priority = WATCHDOG_DEFAULT_PRIORITY - 50;
dev->priv = priv;