[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201022070154.hqvksoj4nss3er2e@bogus>
Date: Thu, 22 Oct 2020 08:02:19 +0100
From: Sudeep Holla <sudeep.holla@....com>
To: Claude Yen <claude.yen@...iatek.com>
Cc: "Rafael J . Wysocki" <rjw@...ysocki.net>,
Len Brown <len.brown@...el.com>, Pavel Machek <pavel@....cz>,
Matthias Brugger <matthias.bgg@...il.com>,
Sudeep Holla <sudeep.holla@....com>, wsd_upstream@...iatek.com,
linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mediatek@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] PM / s2idle: Export s2idle_set_ops
On Thu, Oct 22, 2020 at 02:17:48PM +0800, Claude Yen wrote:
> As suspend_set_ops is exported in commit a5e4fd8783a2
> ("PM / Suspend: Export suspend_set_ops, suspend_valid_only_mem"),
> exporting s2idle_set_ops to make kernel module setup s2idle ops too.
>
> In this way, kernel module can hook platform suspend
> functions regardless of Suspend-to-Ram(S2R) or
> Suspend-to-Idle(S2I)
>
If this is for arm64 platform, then NACK. You must use PSCI and it will
set the ops and it can't be module.
--
Regards,
Sudeep
Powered by blists - more mailing lists