From: Luca Weiss <luca@z3ntu.xyz>
To: ~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Sai Prakash Ranjan <quic_saipraka@quicinc.com>
Cc: linux-arm-msm@vger.kernel.org, linux-watchdog@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
"Luca Weiss" <luca@z3ntu.xyz>,
"Matti Lehtimäki" <matti.lehtimaki@gmail.com>
Subject: [PATCH 0/3] Add watchdog nodes to msm8226 & msm8974
Date: Wed, 11 Oct 2023 18:33:12 +0200 [thread overview]
Message-ID: <20231011-msm8226-msm8974-watchdog-v1-0-2c472818fbce@z3ntu.xyz> (raw)
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.
This behavior has been observed on both msm8974 and msm8226 smartphones.
Signed-off-by: Luca Weiss <luca@z3ntu.xyz>
---
Matti Lehtimäki (3):
dt-bindings: watchdog: qcom-wdt: Add MSM8226 and MSM8974 compatibles
ARM: dts: qcom: msm8226: Add watchdog node
ARM: dts: qcom: msm8974: Add watchdog node
Documentation/devicetree/bindings/watchdog/qcom-wdt.yaml | 2 ++
arch/arm/boot/dts/qcom/qcom-msm8226.dtsi | 8 ++++++++
arch/arm/boot/dts/qcom/qcom-msm8974.dtsi | 8 ++++++++
3 files changed, 18 insertions(+)
---
base-commit: 2933a1156742d8c47550493a77af8e2d81cf3c84
change-id: 20231011-msm8226-msm8974-watchdog-a88e45f4e2a4
Best regards,
--
Luca Weiss <luca@z3ntu.xyz>
next reply other threads:[~2023-10-11 16:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 16:33 Luca Weiss [this message]
2023-10-11 16:33 ` [PATCH 1/3] dt-bindings: watchdog: qcom-wdt: Add MSM8226 and MSM8974 compatibles Luca Weiss
2023-10-11 18:27 ` Krzysztof Kozlowski
2023-10-11 21:11 ` Guenter Roeck
2023-10-11 16:33 ` [PATCH 2/3] ARM: dts: qcom: msm8226: Add watchdog node Luca Weiss
2023-10-11 18:29 ` Konrad Dybcio
2023-10-11 16:33 ` [PATCH 3/3] ARM: dts: qcom: msm8974: " Luca Weiss
2023-10-11 18:29 ` Konrad Dybcio
2023-12-03 4:54 ` (subset) [PATCH 0/3] Add watchdog nodes to msm8226 & msm8974 Bjorn Andersson
2023-12-03 10:12 ` Luca Weiss
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=20231011-msm8226-msm8974-watchdog-v1-0-2c472818fbce@z3ntu.xyz \
--to=luca@z3ntu.xyz \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=matti.lehtimaki@gmail.com \
--cc=phone-devel@vger.kernel.org \
--cc=quic_saipraka@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=wim@linux-watchdog.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).