From: sashiko-bot@kernel.org
To: "Rosen Penev" <rosenp@gmail.com>
Cc: "Alexandre Belloni" <alexandre.belloni@bootlin.com>,
linux-rtc@vger.kernel.org
Subject: Re: [PATCH] rtc: omap: fail rtc-only suspend without a power-off RTC
Date: Sun, 04 Oct 2026 22:10:15 +0000 [thread overview]
Message-ID: <20261004221015.84E521F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20261004215843.396867-1-rosenp@gmail.com>
> omap_rtc_power_off_program() dereferences omap_rtc_power_off_rtc
> unconditionally, but that pointer is only set when an RTC with the
> "system-power-controller" property probed while pm_power_off was still
> free, and it is cleared again when that RTC is removed.
>
> pm33xx uses the function for rtc-only suspend whenever off mode is
> enabled and an "rtc0" class device exists, which guarantees none of
> that. Without the property, with another driver owning pm_power_off,
> or with a different RTC registered as rtc0, suspending to mem
> dereferences NULL in the cpu_suspend() finisher.
>
> Return -ENODEV when no power-off RTC is set up, and propagate it from
> am33xx_rtc_only_idle(). A non-zero return from the finisher makes
> cpu_suspend() abort, so pm33xx reports a suspend failure instead of
> oopsing.
>
> Fixes: 5a99ae0092fe ("soc: ti: pm33xx: AM437X: Add rtc_only with ddr in self-refresh support")
> Assisted-by: LLM
> Signed-off-by: Rosen Penev <rosenp@gmail.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261004215843.396867-1-rosenp@gmail.com?part=1
prev parent reply other threads:[~2026-10-04 22:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 21:58 [PATCH] rtc: omap: fail rtc-only suspend without a power-off RTC Rosen Penev
2026-10-04 22:10 ` sashiko-bot [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=20261004221015.84E521F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-rtc@vger.kernel.org \
--cc=rosenp@gmail.com \
--cc=sashiko-reviews@lists.linux.dev \
/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