From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Lina Iyer <ilina@codeaurora.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux PM <linux-pm@vger.kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH] cpuidle: governor: export cpuidle governor functions
Date: Fri, 9 Oct 2020 22:26:10 +0200 [thread overview]
Message-ID: <bd62ffea-9736-f8f7-6a48-13e81f802aea@linaro.org> (raw)
In-Reply-To: <CAJZ5v0ipDRkPe6N9B6RzvHyCBobz8B9EoBfPh4DANrL_e86+Ww@mail.gmail.com>
Hi Rafael,
On 22/09/2020 19:27, Rafael J. Wysocki wrote:
> Hi Lina,
>
> On Tue, Sep 22, 2020 at 6:12 PM Lina Iyer <ilina@codeaurora.org> wrote:
>>
>> Hi Rafael,
>>
>> On Tue, Sep 22 2020 at 10:00 -0600, Rafael J. Wysocki wrote:
>>> Sorry for the delay.
>>>
>>> On Wed, Sep 9, 2020 at 12:15 AM Lina Iyer <ilina@codeaurora.org> wrote:
>>>>
>>>> Commit 83788c0caed3 ("cpuidle: remove unused exports") removed
>>>> capability of registering cpuidle governors, which was unused at that
>>>> time. By exporting the symbol, let's allow platform specific modules to
>>>> register cpuidle governors and use cpuidle_governor_latency_req() to get
>>>> the QoS for the CPU.
>>>
>>> Which platform-specific modules may want to do that and why?
>>>
>> We are planning a custom cpuidle governor for QCOM SoCs. With Android,
>> the idea is to make them loadable modules so they can be in a separate
>> partition.
>
> Well, the $subject patch is not applicable without a mainline user
> requiring this, so it needs to be posted along with that user.
Putting apart the custom cpuidle governor mentioned above, would it make
sense to convert the governors into modules ? It is pointless to have
all of them compiled in, especially with distros doing make
allmodconfig, no?
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2020-10-09 20:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 22:15 [PATCH] cpuidle: governor: export cpuidle governor functions Lina Iyer
2020-09-22 16:00 ` Rafael J. Wysocki
2020-09-22 16:12 ` Lina Iyer
2020-09-22 17:27 ` Rafael J. Wysocki
2020-10-09 20:26 ` Daniel Lezcano [this message]
2021-08-17 9:31 ` Maulik Shah
2021-08-19 15:02 ` Ulf Hansson
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=bd62ffea-9736-f8f7-6a48-13e81f802aea@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=ilina@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
/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).