From: Maulik Shah <quic_mkshah@quicinc.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>, <quic_lsrao@quicinc.com>,
"Nayak, Rajendra" <rnayak@codeaurora.org>
Subject: Re: [PATCH 0/4] Allow cpuidle governors to be compiled as modules
Date: Thu, 25 Nov 2021 18:48:16 +0530 [thread overview]
Message-ID: <ac35bafa-a57f-e9ea-4dee-9af547de34e2@quicinc.com> (raw)
In-Reply-To: <CAJZ5v0hhUSjNdHwF4dRUQ1Fgos-jqg1agHBShhhwFUGK6wiedQ@mail.gmail.com>
Hi Rafael,
On 11/25/2021 5:57 PM, Rafael J. Wysocki wrote:
> On Thu, Nov 25, 2021 at 9:55 AM Maulik Shah <quic_mkshah@quicinc.com> wrote:
>> This series makes changes to allow cpuidle governors menu, ladder and teo
>> to compiled as modules when building with allmodconfig.
> What's the purpose of this?
There are two purposes of this series.
1. The series enables cpuidle governors to be allowed to compiled as
modules.
This is something similar to what cpufreq/devfreq governors do
today as they can be be compiled as modules or built-in depending on the
build config.
2. The series will also enable custom cpuidle governor to be able to
register with cpuidle framework by using cpuidle_register_governor() API.
This will be already achieved by (1) since it will export the
required APIs for menu/ladder/teo governors to be compiled as module.
Thanks,
Maulik
next prev parent reply other threads:[~2021-11-25 13:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 8:54 [PATCH 0/4] Allow cpuidle governors to be compiled as modules Maulik Shah
2021-11-25 8:54 ` [PATCH 1/4] tick/sched: Export symbols used by cpuidle governors Maulik Shah
2021-11-30 23:12 ` Thomas Gleixner
2021-11-25 8:54 ` [PATCH 2/4] sched/core: " Maulik Shah
2021-11-25 9:35 ` Peter Zijlstra
2021-11-25 13:31 ` Maulik Shah
2021-11-26 16:34 ` Peter Zijlstra
2021-11-25 8:54 ` [PATCH 3/4] cpuidle: governor: export cpuidle governor functions Maulik Shah
2021-11-25 8:54 ` [PATCH 4/4] cpuidle: governors: Allow the governors to be compiled as modules Maulik Shah
2021-11-25 12:27 ` [PATCH 0/4] Allow cpuidle " Rafael J. Wysocki
2021-11-25 13:18 ` Maulik Shah [this message]
2021-11-25 15:46 ` Rafael J. Wysocki
2021-11-25 17:16 ` Doug Smythies
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=ac35bafa-a57f-e9ea-4dee-9af547de34e2@quicinc.com \
--to=quic_mkshah@quicinc.com \
--cc=bjorn.andersson@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=quic_lsrao@quicinc.com \
--cc=rafael@kernel.org \
--cc=rnayak@codeaurora.org \
--cc=ulf.hansson@linaro.org \
/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;
as well as URLs for NNTP newsgroup(s).