From: Claudiu Beznea <claudiu.beznea@kernel.org>
To: Ovidiu Panait <ovidiu.panait.rb@renesas.com>,
rafael@kernel.org, lenb@kernel.org, pavel@kernel.org
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PM: suspend: Do not call suspend_ops->begin()/end() for s2idle
Date: Mon, 12 Oct 2026 12:42:15 +0300 [thread overview]
Message-ID: <d11e7da8-9202-4b9f-b915-155f9185770f@kernel.org> (raw)
In-Reply-To: <20261005111157.17256-1-ovidiu.panait.rb@renesas.com>
On 10/5/26 14:11, Ovidiu Panait wrote:
> Commit 7602c0ec0bbf ("firmware: psci: Set
> pm_set_resume/suspend_via_firmware() for SYSTEM_SUSPEND") made
> psci_system_suspend_begin() call pm_set_suspend_via_firmware(), so that
> device drivers can prepare for the possible removal of the power before
> PSCI SYSTEM_SUSPEND.
>
> Since then, on platforms where PSCI firmware supports SYSTEM_SUSPEND,
> pm_suspend_via_firmware() returns true during both s2ram and s2idle.
> This is inconsistent, since SYSTEM_SUSPEND is only invoked for s2ram.
>
> This was observed while investigating PCI-related suspend/resume issues
> on Renesas platforms (RZ/G3S, RZ/V2H), and was traced to
> platform_suspend_begin() falling back to suspend_ops->begin() (PSCI in
> this case) when there is no s2idle_ops->begin() callback:
>
> platform_suspend_begin(PM_SUSPEND_TO_IDLE)
> suspend_ops->begin()
> psci_system_suspend_begin()
> pm_set_suspend_via_firmware()
>
> platform_resume_end() falls back to suspend_ops->end() in the same way.
>
> Since s2idle has its own set of callbacks in s2idle_ops, make
> platform_suspend_begin() and platform_resume_end() only invoke those for
> s2idle, like the other platform_*() helpers do.
>
> Signed-off-by: Ovidiu Panait<ovidiu.panait.rb@renesas.com>
Tested it on top of
https://lore.kernel.org/all/20261007053645.1391545-1-claudiu.beznea@kernel.org
You can add:
Tested-by: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
Should "Fixes:" tag be added as well?
Thank you,
Claudiu
prev parent reply other threads:[~2026-10-12 9:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 11:11 Ovidiu Panait
2026-10-12 9:42 ` Claudiu Beznea [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=d11e7da8-9202-4b9f-b915-155f9185770f@kernel.org \
--to=claudiu.beznea@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=ovidiu.panait.rb@renesas.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
all inboxes | Powered by JetHome®