linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maulik Shah <mkshah@codeaurora.org>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Linux PM <linux-pm@vger.kernel.org>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	Saravana Kannan <saravanak@google.com>,
	Todd Kjos <tkjos@google.com>,
	Srinivas Rao L <lsrao@codeaurora.org>
Subject: Re: [PATCH] cpuidle: governor: export cpuidle governor functions
Date: Tue, 17 Aug 2021 15:01:49 +0530	[thread overview]
Message-ID: <2fe42a4d-469a-0424-45d4-5d7027c88263@codeaurora.org> (raw)
In-Reply-To: <bd62ffea-9736-f8f7-6a48-13e81f802aea@linaro.org>

Hi Daniel/Rafael,

 >> would it make sense to convert the governors into modules

i am not aware if this was not pursued further due to any issue.

Do you see any concerns to allow existing governors compiled as loadable 
module?
if not i can work on same and post. please do let me know your thoughts 
on this.

i have CCed Saravana and Todd for awareness.

Thanks,
Maulik

On 10/10/2020 1:56 AM, Daniel Lezcano wrote:
> 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?
>
>
-- 
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation


  reply	other threads:[~2021-08-17  9:32 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
2021-08-17  9:31         ` Maulik Shah [this message]
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=2fe42a4d-469a-0424-45d4-5d7027c88263@codeaurora.org \
    --to=mkshah@codeaurora.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lsrao@codeaurora.org \
    --cc=rafael@kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=saravanak@google.com \
    --cc=tkjos@google.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;
as well as URLs for NNTP newsgroup(s).