From: Michael Walle <michael@walle.cc>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Cc: andre.przywara@arm.com, etienne.carriere@linaro.org,
ilias.apalodimas@linaro.org, sjg@chromium.org,
trini@konsulko.com, u-boot@lists.denx.de,
rasmus.villemoes@prevas.dk
Subject: Re: [PATCH 1/1] efi_loader: stop watchdogs in ExitBootServices()
Date: Tue, 07 Feb 2023 16:34:30 +0100 [thread overview]
Message-ID: <d5e18468df0e0f00faf4dc1bacf619fa@walle.cc> (raw)
In-Reply-To: <f22cd8bb-f113-6eb1-81e2-cde1108523e9@canonical.com>
>>>> Basically I want the following:
>>>>
>>>> (1) board boots with watchdog enabled
>>>> (2) u-boot services watchdog
>>>> (3a) booting embedded linux with booti (watchdog enabled) or
>>>> (3b) booting generic OS with bootefi (watchdog disabled)
>>>>
>>>> The missing case is booting an embedded linux with bootefi, which
>>>> would be nice to have. But I don't really see it as a use-case for
>>>> our board.
>>>>
>>> For SUNXI boards disabling CONFIG_WATCHDOG_AUTOSTART solved the
>>> problem with the very short maximum expiration time of the watchdog.
>>
>> I can't follow you here. What "very short maximum expiration time"?
>> With CONFIG_WATCHDOG_AUTOSTART disabled, the watchdog won't be kicked
>> by u-boot, right? wdt->running will never be set to true and
>> wdt_cyclic() will be a noop.
>
> The sunxi boards failed to boot with CONFIG_WATCHDOG_AUTOSTART because
> 16s is too short for Linux to install a watchdog driver. With
> CONFIG_WATCHDOG_AUTOSTART=n the watchdog is not running and the boards
> boot.
But how does that help in my case?
-michael
next prev parent reply other threads:[~2023-02-07 15:34 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-28 8:57 [PATCH 1/1] efi_loader: stop watchdogs in ExitBootServices() Heinrich Schuchardt
2023-01-30 18:13 ` Tom Rini
2023-01-30 18:30 ` Tom Rini
2023-01-31 12:03 ` Ilias Apalodimas
2023-01-31 14:16 ` Simon Glass
2023-01-31 14:48 ` Heinrich Schuchardt
2023-01-31 15:07 ` Tom Rini
2023-02-01 8:32 ` Rasmus Villemoes
2023-02-01 9:00 ` Heinrich Schuchardt
2023-02-02 8:17 ` Etienne Carriere
2023-02-02 17:12 ` Simon Glass
2023-02-02 17:22 ` Tom Rini
2023-02-03 2:15 ` Simon Glass
2023-02-03 7:30 ` Rasmus Villemoes
2023-02-07 14:59 ` Michael Walle
2023-02-07 15:08 ` Heinrich Schuchardt
2023-02-07 15:29 ` Michael Walle
2023-02-07 15:30 ` Heinrich Schuchardt
2023-02-07 15:34 ` Michael Walle [this message]
2023-02-03 15:51 ` Tom Rini
2023-02-04 0:20 ` Simon Glass
2023-02-01 12:49 ` Mark Kettenis
2023-02-01 15:21 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2021-11-09 10:19 Heinrich Schuchardt
2021-11-09 10:19 ` Heinrich Schuchardt
2021-11-09 14:20 ` Michael Walle
2021-11-09 14:46 ` Mark Kettenis
2021-11-09 14:54 ` Michael Walle
2021-11-09 17:30 ` Heinrich Schuchardt
2021-11-09 17:55 ` Tom Rini
2021-11-09 18:15 ` Heinrich Schuchardt
2021-11-09 18:18 ` Tom Rini
2021-11-09 21:47 ` Andre Przywara
2021-11-09 23:45 ` Grant Likely
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d5e18468df0e0f00faf4dc1bacf619fa@walle.cc \
--to=michael@walle.cc \
--cc=andre.przywara@arm.com \
--cc=etienne.carriere@linaro.org \
--cc=heinrich.schuchardt@canonical.com \
--cc=ilias.apalodimas@linaro.org \
--cc=rasmus.villemoes@prevas.dk \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.