From: Sudeep Holla <sudeep.holla@arm.com>
To: Samuel Holland <samuel@sholland.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Dmitry Osipenko <dmitry.osipenko@collabora.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
John Ogness <john.ogness@linutronix.de>,
Kai-Heng Feng <kai.heng.feng@canonical.com>,
Luis Chamberlain <mcgrof@kernel.org>,
Petr Mladek <pmladek@suse.com>,
YueHaibing <yuehaibing@huawei.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, tangmeng <tangmeng@uniontech.com>
Subject: Re: [PATCH v2 2/2] firmware/psci: Switch to the sys-off handler API
Date: Wed, 25 Jan 2023 16:50:15 +0000 [thread overview]
Message-ID: <20230125165015.cpar5hcw53wq5rek@bogus> (raw)
In-Reply-To: <20230101181715.42199-3-samuel@sholland.org>
On Sun, Jan 01, 2023 at 12:17:15PM -0600, Samuel Holland wrote:
> Any other poweroff handlers registered at the default priority will
> run before the legacy pm_power_off() function. Register the PSCI
> poweroff handler with the correct priority to ensure it runs first.
>
> PSCI_0_2_FN_SYSTEM_OFF never returns, so the value returned from
> psci_sys_poweroff() is meaningless, but that function must return
> some value to have the right prototype for a notifier callback.
>
Reviewed-by: Sudeep Holla <sudeep.holla@arm.com>
Tested-by: Sudeep Holla <sudeep.holla@arm.com>
--
Regards,
Sudeep
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-01-25 16:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-01 18:17 [PATCH v2 0/2] firmware/psci: Switch to the sys-off handler API Samuel Holland
2023-01-01 18:17 ` [PATCH v2 1/2] kernel/reboot: Use the static sys-off handler for any priority Samuel Holland
2023-01-01 18:17 ` [PATCH v2 2/2] firmware/psci: Switch to the sys-off handler API Samuel Holland
2023-01-25 16:50 ` Sudeep Holla [this message]
2023-01-25 12:53 ` [PATCH v2 0/2] " Dmitry Osipenko
2023-02-07 3:32 ` Samuel Holland
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=20230125165015.cpar5hcw53wq5rek@bogus \
--to=sudeep.holla@arm.com \
--cc=dmitry.osipenko@collabora.com \
--cc=john.ogness@linutronix.de \
--cc=kai.heng.feng@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mark.rutland@arm.com \
--cc=mcgrof@kernel.org \
--cc=pmladek@suse.com \
--cc=rafael.j.wysocki@intel.com \
--cc=samuel@sholland.org \
--cc=tangmeng@uniontech.com \
--cc=yuehaibing@huawei.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