From: Jon Hunter <jonathanh@nvidia.com>
To: Daniel Lezcano <daniel.lezcano@kernel.org>,
Thomas Gleixner <tglx@kernel.org>,
Thierry Reding <thierry.reding@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
Pohsun Su <pohsuns@nvidia.com>, Jon Hunter <jonathanh@nvidia.com>
Subject: [PATCH] clocksource/drivers/timer-tegra186: Use NOIRQ suspend/resume
Date: Mon, 16 Nov 2026 09:18:56 +0000 [thread overview]
Message-ID: <20261116-tegra-clocksource-v1-1-e7988fc2a7d3@nvidia.com> (raw)
From: Pohsun Su <pohsuns@nvidia.com>
Update the Tegra186 Timer driver to use NOIRQ suspend/resume so that the
watchdog is kept active during normal and late suspend/resume phases.
This allows the watchdog to reset the device if any issues occurs during
these suspend/resume phases.
Signed-off-by: Pohsun Su <pohsuns@nvidia.com>
Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
---
drivers/clocksource/timer-tegra186.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/clocksource/timer-tegra186.c b/drivers/clocksource/timer-tegra186.c
index 7938fc4eb1a8..5ac724b83159 100644
--- a/drivers/clocksource/timer-tegra186.c
+++ b/drivers/clocksource/timer-tegra186.c
@@ -589,8 +589,9 @@ static int __maybe_unused tegra186_timer_resume(struct device *dev)
return 0;
}
-static SIMPLE_DEV_PM_OPS(tegra186_timer_pm_ops, tegra186_timer_suspend,
- tegra186_timer_resume);
+static const struct dev_pm_ops tegra186_timer_pm_ops = {
+ SET_NOIRQ_SYSTEM_SLEEP_PM_OPS(tegra186_timer_suspend, tegra186_timer_resume)
+};
static const struct tegra186_timer_soc tegra186_timer = {
.num_timers = 10,
---
base-commit: 84abb955b1015477aa11a96e2f3ac1b938b77f48
change-id: 20261116-tegra-clocksource-870a4fab36f1
Best regards,
--
Jon Hunter <jonathanh@nvidia.com>
reply other threads:[~2026-11-16 9:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261116-tegra-clocksource-v1-1-e7988fc2a7d3@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=daniel.lezcano@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=pohsuns@nvidia.com \
--cc=tglx@kernel.org \
--cc=thierry.reding@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
all inboxes | Powered by JetHome®