public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: lina.iyer@linaro•org (Lina Iyer)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v7 5/7] qcom: cpuidle: Add cpuidle driver for QCOM cpus
Date: Tue, 30 Sep 2014 14:36:52 -0600	[thread overview]
Message-ID: <20140930203652.GE528@ilina-mac.local> (raw)
In-Reply-To: <7h8ul1x86o.fsf@deeprootsystems.com>

On Tue, Sep 30 2014 at 12:41 -0600, Kevin Hilman wrote:
>Nicolas Pitre <nicolas.pitre@linaro•org> writes:
>
>> On Tue, 30 Sep 2014, Kevin Hilman wrote:
>>
>>> On Tue, Sep 30, 2014 at 10:51 AM, Nicolas Pitre
>>> <nicolas.pitre@linaro•org> wrote:
>>> > On Tue, 30 Sep 2014, Kevin Hilman wrote:
>>> >
>>> >> Lorenzo Pieralisi <lorenzo.pieralisi@arm•com> writes:
>
>[...]
>
>>> >> > This may be misleading. Call it PlatformWFI or something like that, not WFI if
>>> >> > that's not what it is.
>>> >>
>>> >> This gets at a little pet peeve of mine:
>>> >>
>>> >> IMO, naming any state with "WFI" is a bit confusing, because typically
>>> >> *every* idle state is entered by one (or more) CPU executing WFI, no?
>>> >
>>> > Agreed.
>>> >
>>> > The only state called "WFI" should be the one that only executes the WFI
>>> > instruction without any other hardware setup around it.
>>>
>>> Well, I would go even further in that none of the states should be
>>> called WFI, because WFI is used to enter all of them.
>>
>> Fair enough.
>>
>> So let's fix this by finding a name for that state that consists of only
>> executing WFI and that every SOC has.
>>
>> Suggestions?
>
>The DT idle-states binding doc (though seemingly written more with
>arm64 and SBSA in mind) uses "standby" for the shallowest idle.
>
Standby - looks good to me.

  reply	other threads:[~2014-09-30 20:36 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-27  0:58 [PATCH v7 0/7] QCOM 8974 and 8084 cpuidle driver Lina Iyer
2014-09-27  0:58 ` [PATCH v7 1/7] qcom: spm: Add Subsystem Power Manager driver Lina Iyer
2014-09-27  8:07   ` Pramod Gurav
2014-09-29 10:29   ` Pramod Gurav
2014-09-29 23:19   ` Stephen Boyd
2014-09-30 16:27     ` Lina Iyer
2014-09-30 17:26   ` Kevin Hilman
2014-09-30 21:18     ` Lina Iyer
2014-09-27  0:58 ` [PATCH v7 2/7] arm: dts: qcom: Add SPM device bindings for 8974 Lina Iyer
2014-09-29 23:02   ` Stephen Boyd
2014-09-27  0:58 ` [PATCH v7 3/7] arm: dts: qcom: Add SPM device bindings for 8084 Lina Iyer
2014-09-30 17:31   ` Kevin Hilman
2014-09-27  0:58 ` [PATCH v7 4/7] qcom: pm: Add cpu low power mode functions Lina Iyer
2014-09-27  8:22   ` Pramod Gurav
2014-09-29 23:37   ` Stephen Boyd
2014-09-30 16:03     ` Lina Iyer
2014-09-30 17:35       ` Kevin Hilman
2014-10-02  0:10       ` Stephen Boyd
2014-10-02  9:50   ` Lorenzo Pieralisi
2014-10-06 17:10     ` Lina Iyer
2014-09-27  0:58 ` [PATCH v7 5/7] qcom: cpuidle: Add cpuidle driver for QCOM cpus Lina Iyer
2014-09-27  8:18   ` Pramod Gurav
2014-09-29 10:31   ` Pramod Gurav
2014-09-29 15:04     ` Lina Iyer
2014-09-29 15:31   ` Lorenzo Pieralisi
2014-09-29 16:16     ` Lina Iyer
2014-09-29 17:22       ` Lorenzo Pieralisi
2014-09-30 17:41     ` Kevin Hilman
2014-09-30 17:51       ` Nicolas Pitre
2014-09-30 18:06         ` Kevin Hilman
2014-09-30 18:30           ` Nicolas Pitre
2014-09-30 18:41             ` Kevin Hilman
2014-09-30 20:36               ` Lina Iyer [this message]
2014-09-29 23:18   ` Stephen Boyd
2014-09-30  8:58     ` Lorenzo Pieralisi
2014-09-30 15:46       ` Lina Iyer
2014-09-30 15:41     ` Lina Iyer
2014-09-27  0:58 ` [PATCH v7 6/7] arm: dts: qcom: Add idle states device nodes for 8974 Lina Iyer
2014-09-27  0:58 ` [PATCH v7 7/7] arm: dts: qcom: Add idle states device nodes for 8084 Lina Iyer
2014-09-29 12:21 ` [PATCH v7 0/7] QCOM 8974 and 8084 cpuidle driver Pramod Gurav
2014-09-29 15:05   ` Lina Iyer

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=20140930203652.GE528@ilina-mac.local \
    --to=lina.iyer@linaro$(echo .)org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /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