[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230125165015.cpar5hcw53wq5rek@bogus>
Date: Wed, 25 Jan 2023 16:50:15 +0000
From: Sudeep Holla <sudeep.holla@....com>
To: Samuel Holland <samuel@...lland.org>
Cc: Mark Rutland <mark.rutland@....com>,
Lorenzo Pieralisi <lpieralisi@...nel.org>,
Dmitry Osipenko <dmitry.osipenko@...labora.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@...el.com>,
John Ogness <john.ogness@...utronix.de>,
Kai-Heng Feng <kai.heng.feng@...onical.com>,
Luis Chamberlain <mcgrof@...nel.org>,
Petr Mladek <pmladek@...e.com>,
YueHaibing <yuehaibing@...wei.com>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
tangmeng <tangmeng@...ontech.com>
Subject: Re: [PATCH v2 2/2] firmware/psci: Switch to the sys-off handler API
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@....com>
Tested-by: Sudeep Holla <sudeep.holla@....com>
--
Regards,
Sudeep
Powered by blists - more mailing lists