From: claude yen <claude.yen@mediatek.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Len Brown <len.brown@intel.com>,
wsd_upstream <wsd_upstream@mediatek.com>,
Linux PM <linux-pm@vger.kernel.org>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"moderated list:ARM/Mediatek SoC..."
<linux-mediatek@lists.infradead.org>, Pavel Machek <pavel@ucw.cz>,
Sudeep Holla <sudeep.holla@arm.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] PM / s2idle: Export s2idle_set_ops
Date: Mon, 26 Oct 2020 17:55:18 +0800 [thread overview]
Message-ID: <1603706118.2127.2.camel@mtkswgap22> (raw)
In-Reply-To: <CAJZ5v0jJHBBrxANa-+mHFE47TZfE4NKNpgp0-rq2BD=Yw7qMXg@mail.gmail.com>
On Fri, 2020-10-23 at 16:58 +0200, Rafael J. Wysocki wrote:
> On Fri, Oct 23, 2020 at 4:48 PM Sudeep Holla <sudeep.holla@arm.com> wrote:
> >
> > On Fri, Oct 23, 2020 at 12:28:20PM +0800, claude yen wrote:
> > > On Thu, 2020-10-22 at 08:02 +0100, Sudeep Holla wrote:
> > > > 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.
> > > >
> > >
> > > PSCI uses suspend_set_ops instead. And suspend_set_ops has been
> > > exported years ago.
> > >
> > > Suspend-to_Idle(S2I) is another suspend method supported by linux
> > > kernel. The corresponding s2idle_ops can be hooked by s2idle_set_ops
> > > by underlying platforms. For example, S2I is now introduced into
> > > Mediatek SoC platforms. Besides, power management driver is built as
> > > kernel module.
> > >
> > > Mobile platforms are now call for kernel drivers to be kernel modules.
> > > This could help drivers easier to migrate to newer linux kernel.
> > > Ref: https://linuxplumbersconf.org/event/7/contributions/790/
> > >
> >
> > I understand that. But I am interested in looking at the module you want
> > to use this and how that interacts with PSCI. If this is arm64, you must
> > use PSCI for system suspend and cpu suspend. What does this module do on
> > top of those is what I want to know. Please post that module or point
> > me if it is already present in the tree.
>
> Regardless, generally speaking, patches that export stuff to modules
> without an in-the-tree user needing this are not applicable to the
> mainline kernel source tree IMV.
>
> Cheers!
Thank for your feedbacks!
Indeed, there is no actual kernel module which uses s2idle_set_ops in
Mainline kernel right now.
However, Google recently ask SoC vendors to build drivers as kernel
modules for reducing migration efforts. For example, The power
management driver on Mediatek platform is now built as vendor module,
which has no plan to upstream so far.
From Mainline kernel's perspective, I am wondering whether such vendor
modules are applicable to export APIs. Exporting APIs only at Google's
Android Common Kernel is an option, but this would make Android Kernel
and Mainline kernel much more diverse.
Regards,
Claude
_______________________________________________
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-26 10:00 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
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 [this message]
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=1603706118.2127.2.camel@mtkswgap22 \
--to=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=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=sudeep.holla@arm.com \
--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