From: Trilok Soni <trilokkumar.soni@oss.qualcomm.com>
To: Zhang Jiaxi <Z1529105815@outlook.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] watchdog: gunyah: report system sleep operation failures
Date: Thu, 8 Oct 2026 18:07:07 -0700 [thread overview]
Message-ID: <ec393b82-912e-4f85-8f30-b3b8cbe948b9@oss.qualcomm.com> (raw)
In-Reply-To: <SY5PR01MB10600A249F7E2CAE647EFD46FA1932@SY5PR01MB10600.ausprd01.prod.outlook.com>
On 10/8/2026 3:34 PM, Zhang Jiaxi wrote:
> From: Jiaxi Zhang <z1529105815@outlook.com>
>
> The system-sleep callbacks discard the errors returned by the watchdog
> start and stop operations and always report success. If stopping an
> active watchdog fails, the PM core can proceed to suspend while the
> watchdog is still counting. Failed restart on resume is also hidden from
> the PM core's callback error reporting.
>
> Return the existing operation result when the watchdog is active. Keep
> inactive callbacks as no-ops. The start/stop command sequence, initial
> activation exception, probe registration and last-resort restart behavior
> are unchanged. Reporting a resume error does not implement recovery or
> guarantee that watchdog protection has been restored.
>
> Signed-off-by: Jiaxi Zhang <z1529105815@outlook.com>
I see flurry of emails from you. What exactly are you testing here? Is this driven
through LLM?
Please also fix your SOB line.
> ---
> Clang 22.1.8 compiled the changed object on torvalds/linux
> 6c377d19d4a5116d9bec5203aa3c6c11523e7898 without diagnostics.
> Actual callback tests with modeled start/stop returns cover error propagation
> and inactive no-ops, including old-code negatives. No device PM or real
> hypervisor-error injection is claimed.
>
> drivers/watchdog/gunyah_wdt.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/watchdog/gunyah_wdt.c b/drivers/watchdog/gunyah_wdt.c
> --- a/drivers/watchdog/gunyah_wdt.c
> +++ b/drivers/watchdog/gunyah_wdt.c
> @@ -214,7 +214,7 @@
> struct watchdog_device *wdd = dev_get_drvdata(dev);
>
> if (watchdog_active(wdd))
> - gunyah_wdt_stop(wdd);
> + return gunyah_wdt_stop(wdd);
>
> return 0;
> }
> @@ -224,7 +224,7 @@
> struct watchdog_device *wdd = dev_get_drvdata(dev);
>
> if (watchdog_active(wdd))
> - gunyah_wdt_start(wdd);
> + return gunyah_wdt_start(wdd);
>
> return 0;
> }
>
next prev parent reply other threads:[~2026-10-09 1:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 22:34 Zhang Jiaxi
2026-10-09 1:07 ` Trilok Soni [this message]
2026-10-09 8:50 ` Zhang Jiaxi
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=ec393b82-912e-4f85-8f30-b3b8cbe948b9@oss.qualcomm.com \
--to=trilokkumar.soni@oss.qualcomm.com \
--cc=Z1529105815@outlook.com \
--cc=andersson@kernel.org \
--cc=konradybcio@kernel.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=wim@linux-watchdog.org \
/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
all inboxes | Powered by JetHome®