[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ac35bafa-a57f-e9ea-4dee-9af547de34e2@quicinc.com>
Date: Thu, 25 Nov 2021 18:48:16 +0530
From: Maulik Shah <quic_mkshah@...cinc.com>
To: "Rafael J. Wysocki" <rafael@...nel.org>
CC: Bjorn Andersson <bjorn.andersson@...aro.org>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
linux-arm-msm <linux-arm-msm@...r.kernel.org>,
Linux PM <linux-pm@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Ulf Hansson <ulf.hansson@...aro.org>, <quic_lsrao@...cinc.com>,
"Nayak, Rajendra" <rnayak@...eaurora.org>
Subject: Re: [PATCH 0/4] Allow cpuidle governors to be compiled as modules
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@...cinc.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
Powered by blists - more mailing lists