From: Tzung-Bi Shih <tzungbi@kernel.org>
To: Doug Anderson <dianders@chromium.org>
Cc: Mayank Rungta <mrungta@google.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Danilo Krummrich <dakr@kernel.org>, Len Brown <lenb@kernel.org>,
Pavel Machek <pavel@kernel.org>,
linux-pm@vger.kernel.org, driver-core@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] PM: sleep: Add DPM watchdog to prepare/late/early/noirq/complete phases
Date: Fri, 11 Sep 2026 13:24:39 +0000 [thread overview]
Message-ID: <aqQBFxCjSdPmFJXh@google.com> (raw)
In-Reply-To: <CAD=FV=WFBmq3kniULxcXNsKgY-Zrb82JfaX5uRWVewQi_tJyJw@mail.gmail.com>
On Thu, Sep 10, 2026 at 10:01:40AM -0700, Doug Anderson wrote:
> On Wed, Sep 9, 2026 at 3:48 PM Mayank Rungta <mrungta@google.com> wrote:
> >
> > Extend the DPM watchdog to wrap device_prepare, device_suspend_late,
> > device_suspend_noirq, device_resume_noirq, device_resume_early, and
> > device_complete callbacks. If a driver hangs during these transitions,
> > the watchdog will fire and dump a stack trace to help identify the
> > offending driver.
> >
> > To prevent false-positive timeouts, the watchdog is set only after
> > waiting for subordinate (during suspend) and superior (during resume)
> > devices. With this change, DPM watchdog coverage is extended across all
> > phases of system sleep transitions.
> >
> > Signed-off-by: Mayank Rungta <mrungta@google.com>
> > ---
> > v2:
> > - Extend DPM watchdog to device_prepare and device_complete callbacks.
> > - Update commit subject and description to reflect coverage across all
> > system sleep phases.
> > v1:
> > - Initial version adding DPM watchdog to late/early/noirq phases.
> >
> > Testing:
> > - Tested on an ARM64 SoC (Pixel platform running a 6.18-based kernel with
> > DPM watchdog enabled; Android 6.18 kernel has latest DPM changes
> > backported).
> > - Verified hang simulation in device_prepare and device_complete
> > triggers DPM watchdog panic and stack trace as expected.
> >
> > drivers/base/power/main.c | 31 ++++++++++++++++++++++++++++---
> > 1 file changed, 28 insertions(+), 3 deletions(-)
>
> Thanks! I guess you dropped my (and Tzung-Bi's) Reviewed-by tags
> because of the minor changes between v1 and v2? They look right to me,
> so:
>
> Reviewed-by: Douglas Anderson <dianders@chromium.org>
They look right to me too:
Reviewed-by: Tzung-Bi Shih <tzungbi@kernel.org>
prev parent reply other threads:[~2026-09-11 13:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 22:48 [PATCH v2] PM: sleep: Add DPM watchdog to prepare/late/early/noirq/complete phases Mayank Rungta
2026-09-10 17:01 ` Doug Anderson
2026-09-11 13:24 ` Tzung-Bi Shih [this message]
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=aqQBFxCjSdPmFJXh@google.com \
--to=tzungbi@kernel.org \
--cc=dakr@kernel.org \
--cc=dianders@chromium.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mrungta@google.com \
--cc=pavel@kernel.org \
--cc=rafael@kernel.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