From: Balbir Singh <bsingharora@gmail•com>
To: Daniel Lezcano <daniel.lezcano@linaro•org>,
"Gautham R. Shenoy" <ego@linux•vnet.ibm.com>,
"Rafael J. Wysocki" <rjw@rjwysocki•net>,
Michael Ellerman <mpe@ellerman•id.au>,
Benjamin Herrenschmidt <benh@kernel•crashing.org>,
Michael Neuling <michael.neuling@au1•ibm.com>,
Paul Mackerras <paulus@samba•org>,
Vaidyanathan Srinivasan <svaidy@linux•vnet.ibm.com>
Cc: linux-kernel@vger•kernel.org, linuxppc-dev@lists•ozlabs.org,
Anton Blanchard <anton@samba•org>,
linux-pm@vger•kernel.org
Subject: Re: [RFC/PATCH 1/2] cpuidle: Allow idle-states to be disabled at start
Date: Thu, 25 Aug 2016 00:48:38 +1000 [thread overview]
Message-ID: <fe9a9667-cbbb-8fa2-5db0-2edd3220ca7b@gmail.com> (raw)
In-Reply-To: <57BDB2D8.4080507@linaro.org>
On 25/08/16 00:44, Daniel Lezcano wrote:
> On 08/19/2016 12:26 AM, Gautham R. Shenoy wrote:
>> From: "Gautham R. Shenoy" <ego@linux•vnet.ibm.com>
>>
>> Currently all the idle states registered by a cpu-idle driver are
>> enabled by default. This patch adds a mechanism which allows the
>> driver to hint if an idle-state should start in a disabled state. The
>> cpu-idle core will use this hint to appropriately initialize the
>> usage->disable knob of the CPU device idle state.
>
> Why do you need to do that ?
>
I think patch 2/2 explains the reason as it uses this infrastructure
Balbir Singh
next prev parent reply other threads:[~2016-08-24 14:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 22:26 [RFC/PATCH 0/2] powernv:cpuidle: Enable winkle idle state Gautham R. Shenoy
2016-08-18 22:26 ` [RFC/PATCH 1/2] cpuidle: Allow idle-states to be disabled at start Gautham R. Shenoy
2016-08-24 14:44 ` Daniel Lezcano
2016-08-24 14:48 ` Balbir Singh [this message]
2016-08-24 15:06 ` Daniel Lezcano
2016-08-25 13:46 ` Balbir Singh
2016-08-25 14:07 ` Daniel Lezcano
2016-08-18 22:26 ` [RFC/PATCH 2/2] powernv:cpuidle: Enable winkle idle state in CPU-Idle Gautham R. Shenoy
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=fe9a9667-cbbb-8fa2-5db0-2edd3220ca7b@gmail.com \
--to=bsingharora@gmail$(echo .)com \
--cc=anton@samba$(echo .)org \
--cc=benh@kernel$(echo .)crashing.org \
--cc=daniel.lezcano@linaro$(echo .)org \
--cc=ego@linux$(echo .)vnet.ibm.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-pm@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=michael.neuling@au1$(echo .)ibm.com \
--cc=mpe@ellerman$(echo .)id.au \
--cc=paulus@samba$(echo .)org \
--cc=rjw@rjwysocki$(echo .)net \
--cc=svaidy@linux$(echo .)vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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