From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from phobos.denx.de (phobos.denx.de [85.214.62.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 415F9C636CD for ; Tue, 7 Feb 2023 15:34:37 +0000 (UTC) Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id 46FB5859C5; Tue, 7 Feb 2023 16:34:35 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=pass (p=quarantine dis=none) header.from=walle.cc Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Authentication-Results: phobos.denx.de; dkim=pass (2048-bit key; secure) header.d=walle.cc header.i=@walle.cc header.b="po/mgAoG"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id 1411C85DDA; Tue, 7 Feb 2023 16:34:34 +0100 (CET) Received: from mail.3ffe.de (0001.3ffe.de [IPv6:2a01:4f8:c0c:9d57::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by phobos.denx.de (Postfix) with ESMTPS id 61C0C85899 for ; Tue, 7 Feb 2023 16:34:31 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=pass (p=quarantine dis=none) header.from=walle.cc Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=michael@walle.cc Received: from 3ffe.de (0001.3ffe.de [IPv6:2a01:4f8:c0c:9d57::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.3ffe.de (Postfix) with ESMTPSA id F0A41135F; Tue, 7 Feb 2023 16:34:30 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walle.cc; s=mail2022082101; t=1675784071; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Fr8c8Bkv/R8+SOsHGP73wRKXCURF4+fVg/LcUeqazG0=; b=po/mgAoGo3+iPVY+461usuIXpohSue16Hfb3lo2L4H+sgd1J0agqVyieNM86EFO1NfYB7O HRFi8h2dPxnHWc189PJ2yf5pKlG7PYrzy6gb8fsKp0BaXFVpZc3JsuL5DFFfFWu4n+RbPd jr1sBBWAzAnT8cGJo5e9ME7evyZr0tTY/LdW5aMGgbFTlBpLb0VMctQYSwuVCi8GUukIsm MS4RAycSDNqRnhHDM0M/i7AhavB6FJPYFsyu9mgjaof+W8wFq9LPeOZwazxgdL/4ofsqjR XWljV3H7aFx2DMsqU7avMO7CT5TD5upcI6aTevCahYLGejwrtX+VTDb77LCjYQ== MIME-Version: 1.0 Date: Tue, 07 Feb 2023 16:34:30 +0100 From: Michael Walle To: Heinrich Schuchardt 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() In-Reply-To: References: <22478c7f-ffa0-0bf7-5473-0ba1ee7478c3@prevas.dk> <20230207145955.2468379-1-michael@walle.cc> <1cda1ca157aae7210f93bea7e9c3f3a1@walle.cc> User-Agent: Roundcube Webmail/1.4.13 Message-ID: X-Sender: michael@walle.cc Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.39 Precedence: list List-Id: U-Boot discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: u-boot-bounces@lists.denx.de Sender: "U-Boot" X-Virus-Scanned: clamav-milter 0.103.6 at phobos.denx.de X-Virus-Status: Clean >>>> 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