From: Samuel Holland <samuel@sholland.org>
To: Dmitry Osipenko <dmitry.osipenko@collabora.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Mark Rutland <mark.rutland@arm.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Samuel Holland <samuel@sholland.org>
Subject: [PATCH 0/2] firmware/psci: Switch to the sys-off handler API
Date: Sat, 5 Nov 2022 16:48:38 -0500 [thread overview]
Message-ID: <20221105214841.7828-1-samuel@sholland.org> (raw)
I am interested in converting the axp20x PMIC driver to use the sys-off
API for its poweroff handler, so it can be used as a fallback for the
SBI poweroff handler on RISC-V. But the PSCI poweroff handler still uses
pm_power_off, so done alone, this would cause the axp20x callback to be
called first, before the PSCI poweroff handler.
In order to prevent this change in behavior, the PSCI poweroff handler
needs to be converted to the sys-off API first, at a higher priority.
This series performs the conversion, after accounting for the fact that
the PSCI poweroff handler is registered quite early during boot.
Samuel Holland (2):
kernel/reboot: Use the static sys-off handler for any priority
firmware/psci: Switch to the sys-off handler API
drivers/firmware/psci/psci.c | 9 ++++++---
kernel/reboot.c | 10 ++++------
2 files changed, 10 insertions(+), 9 deletions(-)
--
2.37.3
next reply other threads:[~2022-11-05 21:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-05 21:48 Samuel Holland [this message]
2022-11-05 21:48 ` [PATCH 1/2] kernel/reboot: Use the static sys-off handler for any priority Samuel Holland
2022-11-06 22:28 ` Dmitry Osipenko
2022-11-05 21:48 ` [PATCH 2/2] firmware/psci: Switch to the sys-off handler API Samuel Holland
2022-11-07 10:55 ` Sudeep Holla
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=20221105214841.7828-1-samuel@sholland.org \
--to=samuel@sholland.org \
--cc=dmitry.osipenko@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mark.rutland@arm.com \
--cc=rafael.j.wysocki@intel.com \
/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®