From: Sudeep Holla <sudeep.holla@arm.com>
To: Claude Yen <claude.yen@mediatek.com>
Cc: Len Brown <len.brown@intel.com>,
wsd_upstream@mediatek.com, linux-pm@vger.kernel.org,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
Pavel Machek <pavel@ucw.cz>, Sudeep Holla <sudeep.holla@arm.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] PM / s2idle: Export s2idle_set_ops
Date: Thu, 22 Oct 2020 08:02:19 +0100 [thread overview]
Message-ID: <20201022070154.hqvksoj4nss3er2e@bogus> (raw)
In-Reply-To: <20201022061748.13730-2-claude.yen@mediatek.com>
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
_______________________________________________
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:[~2020-10-22 7:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 6:17 [PATCH] PM / s2idle: Export s2idle_set_ops Claude Yen
2020-10-22 6:17 ` Claude Yen
2020-10-22 7:02 ` Sudeep Holla [this message]
2020-10-23 4:28 ` claude yen
2020-10-23 14:48 ` Sudeep Holla
2020-10-23 14:58 ` Rafael J. Wysocki
2020-10-26 9:55 ` claude yen
2020-10-24 8:26 ` Christoph Hellwig
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=20201022070154.hqvksoj4nss3er2e@bogus \
--to=sudeep.holla@arm.com \
--cc=claude.yen@mediatek.com \
--cc=len.brown@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
--cc=wsd_upstream@mediatek.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