[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <170157925797.1717511.7301998654173050568.b4-ty@kernel.org>
Date: Sat, 2 Dec 2023 20:54:39 -0800
From: Bjorn Andersson <andersson@...nel.org>
To: ~postmarketos/upstreaming@...ts.sr.ht, phone-devel@...r.kernel.org,
Andy Gross <agross@...nel.org>,
Konrad Dybcio <konrad.dybcio@...aro.org>,
Wim Van Sebroeck <wim@...ux-watchdog.org>,
Guenter Roeck <linux@...ck-us.net>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
Sai Prakash Ranjan <quic_saipraka@...cinc.com>,
Luca Weiss <luca@...tu.xyz>
Cc: linux-arm-msm@...r.kernel.org, linux-watchdog@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
Matti Lehtimäki <matti.lehtimaki@...il.com>
Subject: Re: (subset) [PATCH 0/3] Add watchdog nodes to msm8226 & msm8974
On Wed, 11 Oct 2023 18:33:12 +0200, Luca Weiss wrote:
> Document the compatible for the watchdog found on both SoCs, and add
> them to the SoC dtsi file. And especially for the case where the
> bootloader has already enabled the watchdog we need to start petting it
> on time, otherwise the system gets rebooted.
>
> It's worth noting that the watchdog behaves a bit unexpectedly.
> It appears the watchdog counts down significantly slower when there's no
> load on the system and can last far longer than 30 seconds until they
> bark. Only when putting load on the system, e.g. with stress-ng does the
> watchdog interrupt fire and kill the system within an expected amount of
> time.
>
> [...]
Applied, thanks!
[3/3] ARM: dts: qcom: msm8974: Add watchdog node
commit: 95053f6bc8ffca438a261400d7c06bd74e3f106e
Best regards,
--
Bjorn Andersson <andersson@...nel.org>
Powered by blists - more mailing lists