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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 91A84CFB44F for ; Mon, 7 Oct 2024 18:05:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=lRq9/7xf0OzeeZlZiRi6QM0IOW8jg/QdVQsBpUKBlGY=; b=I9s9HNSZh0Ad+3c4zZIDkVK4dR iWFmDrc8NW0mrVyCNpCfj27ux6LJHVHu6e+XmTGgSs7yfu6ktGiYor3nVbl3M5HzLH15H/dETr7zZ vRYkjBXeHpfn/0Xkxb5082aYHM0wWL6NyXmVtQ0RHwwSLcAhIRC10SPviy6RfRtja2L3wzXDs3yOj QCSUVWJTqfWpRl74rlMbfkTROSJfQeBLfi4sLATsu7alL5gnb6q2PWF+mFjk2MYV//h0bUX8sSUSz 66xqXVhUM2jdvFugTf1FrudpPC9xzBegNpiz+ICm+1cVdT5SgAMwyS0240WijSXx5fvaGqAJmx1Eh wpqFbB8Q==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98 #2 (Red Hat Linux)) id 1sxs74-00000003Q6d-37O3; Mon, 07 Oct 2024 18:05:42 +0000 Received: from nyc.source.kernel.org ([147.75.193.91]) by bombadil.infradead.org with esmtps (Exim 4.98 #2 (Red Hat Linux)) id 1sxs1P-00000003PDq-2MUt for linux-arm-kernel@lists.infradead.org; Mon, 07 Oct 2024 17:59:53 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by nyc.source.kernel.org (Postfix) with ESMTP id 1BBAFA41F4F; Mon, 7 Oct 2024 17:59:42 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3D2DCC4CEC7; Mon, 7 Oct 2024 17:59:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1728323990; bh=nX4QdvK4jon6rwcgdgSFV/YaFDuwES1YhsvSlSFRGic=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=nq+TQvbdERuBePxTB4ZMGYW1C13CoKCVd0CTzUs/6e5JZp9lz7LWMnY57/sPa7Ut+ Tq2Wb6XLhgOBjqavluAa4FJywZOXi1gUtrXOwSX8SskoIfUW18iiEyGkfTIKuteDtX 4t/YsU4EbyaeJF6EIbiQ69mt0mdgw6w5pCcuVb+Ns3R/5WCQZz9axhJDNXP5q22U7b JWdrlOhK062mXhH5jw8fhMHLrXooaKggTmyXSQ8J4t3CCRVkgHH9FzgGgeumVx9VfW ZSQkiocKHFIh1OohSwQnsfwLvIdoOfNCS2kU6e46pQOImlIT74CPnOELVAsNhFF9RD fjA4gNrftwPnA== Date: Mon, 7 Oct 2024 12:59:49 -0500 From: Rob Herring To: Chin-Ting Kuo Cc: patrick@stwcx.xyz, wim@linux-watchdog.org, linux@roeck-us.net, krzk+dt@kernel.org, conor+dt@kernel.org, joel@jms.id.au, andrew@codeconstruct.com.au, linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org, Peter.Yin@quantatw.com, Patrick_NC_Lin@wiwynn.com, Bonnie_Lo@wiwynn.com, DELPHINE_CHIU@wiwynn.com, BMC-SW@aspeedtech.com Subject: Re: [PATCH 1/4] dt-bindings: watchdog: aspeed: Add property for WDT SW reset Message-ID: <20241007175949.GA1738291-robh@kernel.org> References: <20241007063408.2360874-1-chin-ting_kuo@aspeedtech.com> <20241007063408.2360874-2-chin-ting_kuo@aspeedtech.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20241007063408.2360874-2-chin-ting_kuo@aspeedtech.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20241007_105951_697253_CBF7E801 X-CRM114-Status: GOOD ( 17.12 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Mon, Oct 07, 2024 at 02:34:05PM +0800, Chin-Ting Kuo wrote: > Add "aspeed,restart-sw" property to distinguish normal WDT > reset from system restart triggered by SW consciously. > > Signed-off-by: Chin-Ting Kuo > --- > .../bindings/watchdog/aspeed,ast2400-wdt.yaml | 11 +++++++++++ > 1 file changed, 11 insertions(+) > > diff --git a/Documentation/devicetree/bindings/watchdog/aspeed,ast2400-wdt.yaml b/Documentation/devicetree/bindings/watchdog/aspeed,ast2400-wdt.yaml > index be78a9865584..6cc3604c295a 100644 > --- a/Documentation/devicetree/bindings/watchdog/aspeed,ast2400-wdt.yaml > +++ b/Documentation/devicetree/bindings/watchdog/aspeed,ast2400-wdt.yaml > @@ -95,6 +95,17 @@ properties: > array with the first word defined using the AST2600_WDT_RESET1_* macros, > and the second word defined using the AST2600_WDT_RESET2_* macros. > > + aspeed,restart-sw: > + $ref: /schemas/types.yaml#/definitions/flag > + description: > > + Normally, ASPEED WDT reset may occur when system hangs or reboot > + triggered by SW consciously. However, system doesn't know whether the > + restart is triggered by SW consciously since the reset event flag is > + the same as normal WDT timeout reset. With this property, SW can > + restart the system immediately and directly without wait for WDT > + timeout occurs. The reset event flag is also different from the normal > + WDT reset. This property is only supported since AST2600 platform. Why can't this be implicit based on the ast2600 compatible string? Rob