From: Lina Iyer <lina.iyer@linaro.org>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: ulf.hansson@linaro.org, khilman@kernel.org, rjw@rjwysocki.net,
linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
geert@linux-m68k.org, k.kozlowski@samsung.com,
msivasub@codeaurora.org, agross@codeaurora.org,
linux-arm-msm@vger.kernel.org, lorenzo.pieralisi@arm.com,
ahaslam@baylibre.com, mtitinger@baylibre.com,
devicetree@vger.kernel.org
Subject: Re: [RFC v2 12/12] ARM64: dts: Define CPU power domain for MSM8916
Date: Tue, 1 Mar 2016 12:41:49 -0700 [thread overview]
Message-ID: <20160301194149.GP1440@linaro.org> (raw)
In-Reply-To: <20160226195035.GA28849@codeaurora.org>
On Fri, Feb 26 2016 at 12:50 -0700, Stephen Boyd wrote:
>On 02/12, Lina Iyer wrote:
>> @@ -101,6 +105,27 @@
>> };
>> };
>>
>> + CPU_PD: cpu-pd@0 {
>> + #power-domain-cells = <0>;
>> + power-states = <&CLUSTER_RET>, <&CLUSTER_PWR_DWN>;
>
>Why isn't this part of the psci node? PSCI is the node that's
>providing the code/logic for the power domain.
>
I like that idea too.
Lorenzo, what do you think?
>> + };
>> +
>> + pd-power-states {
>> + CLUSTER_RET: power-state@1 {
>> + state-param = <0x1000010>;
>> + entry-latency-us = <500>;
>> + exit-latency-us = <500>;
>> + residency-us = <2000>;
>> + };
>> +
>> + CLUSTER_PWR_DWN: power-state@2 {
>> + state-param = <0x1000030>;
>> + entry-latency-us = <2000>;
>> + exit-latency-us = <2000>;
>> + residency-us = <6000>;
>> + };
>> + };
>> +
>
>And I would expect these to be put somewhere inside the power
>domain provider as well? Is this documented somewhere?
>
Not yet, they will be, when it is submitted. This the glue patch that I
use on top of Axel's series to read domain states from DT, instead of
defining with the driver.
I have to discuss with Ulf, as to who is submitting that patch.
Thanks,
Lina
>> psci {
>> compatible = "arm,psci-1.0";
>> method = "smc";
>
>--
>Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
>a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: lina.iyer@linaro.org (Lina Iyer)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC v2 12/12] ARM64: dts: Define CPU power domain for MSM8916
Date: Tue, 1 Mar 2016 12:41:49 -0700 [thread overview]
Message-ID: <20160301194149.GP1440@linaro.org> (raw)
In-Reply-To: <20160226195035.GA28849@codeaurora.org>
On Fri, Feb 26 2016 at 12:50 -0700, Stephen Boyd wrote:
>On 02/12, Lina Iyer wrote:
>> @@ -101,6 +105,27 @@
>> };
>> };
>>
>> + CPU_PD: cpu-pd at 0 {
>> + #power-domain-cells = <0>;
>> + power-states = <&CLUSTER_RET>, <&CLUSTER_PWR_DWN>;
>
>Why isn't this part of the psci node? PSCI is the node that's
>providing the code/logic for the power domain.
>
I like that idea too.
Lorenzo, what do you think?
>> + };
>> +
>> + pd-power-states {
>> + CLUSTER_RET: power-state at 1 {
>> + state-param = <0x1000010>;
>> + entry-latency-us = <500>;
>> + exit-latency-us = <500>;
>> + residency-us = <2000>;
>> + };
>> +
>> + CLUSTER_PWR_DWN: power-state at 2 {
>> + state-param = <0x1000030>;
>> + entry-latency-us = <2000>;
>> + exit-latency-us = <2000>;
>> + residency-us = <6000>;
>> + };
>> + };
>> +
>
>And I would expect these to be put somewhere inside the power
>domain provider as well? Is this documented somewhere?
>
Not yet, they will be, when it is submitted. This the glue patch that I
use on top of Axel's series to read domain states from DT, instead of
defining with the driver.
I have to discuss with Ulf, as to who is submitting that patch.
Thanks,
Lina
>> psci {
>> compatible = "arm,psci-1.0";
>> method = "smc";
>
>--
>Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
>a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-03-01 19:41 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 20:50 [RFC v2 00/12] PM: SoC idle support using PM domains Lina Iyer
2016-02-12 20:50 ` Lina Iyer
2016-02-12 20:50 ` [RFC v2 01/12] PM / Domains: Abstract genpd locking Lina Iyer
2016-02-12 20:50 ` Lina Iyer
2016-02-26 18:08 ` Stephen Boyd
2016-02-26 18:08 ` Stephen Boyd
2016-03-01 16:55 ` Lina Iyer
2016-03-01 16:55 ` Lina Iyer
2016-02-12 20:50 ` [RFC v2 02/12] PM / Domains: Support IRQ safe PM domains Lina Iyer
2016-02-12 20:50 ` Lina Iyer
2016-02-26 18:17 ` Stephen Boyd
2016-02-26 18:17 ` Stephen Boyd
2016-03-01 17:44 ` Lina Iyer
2016-03-01 17:44 ` Lina Iyer
2016-02-12 20:50 ` [RFC v2 03/12] PM / cpu_domains: Setup PM domains for CPUs/clusters Lina Iyer
2016-02-12 20:50 ` Lina Iyer
2016-02-17 23:38 ` Lina Iyer
2016-02-17 23:38 ` Lina Iyer
2016-02-18 17:29 ` [BUG FIX] PM / cpu_domains: Check for NULL callbacks Lina Iyer
2016-02-18 17:29 ` Lina Iyer
2016-02-18 17:46 ` Rafael J. Wysocki
2016-02-18 17:46 ` Rafael J. Wysocki
2016-02-18 22:51 ` Lina Iyer
2016-02-18 22:51 ` Lina Iyer
2016-02-26 19:10 ` [RFC v2 03/12] PM / cpu_domains: Setup PM domains for CPUs/clusters Stephen Boyd
2016-02-26 19:10 ` Stephen Boyd
2016-03-01 18:00 ` Lina Iyer
2016-03-01 18:00 ` Lina Iyer
2016-02-12 20:50 ` [RFC v2 04/12] ARM: cpuidle: Add runtime PM support for CPUs Lina Iyer
2016-02-12 20:50 ` Lina Iyer
2016-02-26 18:24 ` Stephen Boyd
2016-02-26 18:24 ` Stephen Boyd
2016-03-01 18:36 ` Lina Iyer
2016-03-01 18:36 ` Lina Iyer
2016-02-12 20:50 ` [RFC v2 05/12] timer: Export next wake up of a CPU Lina Iyer
2016-02-12 20:50 ` Lina Iyer
2016-02-12 20:50 ` [RFC v2 06/12] PM / cpu_domains: Record CPUs that are part of the domain Lina Iyer
2016-02-12 20:50 ` Lina Iyer
2016-02-26 19:20 ` Stephen Boyd
2016-02-26 19:20 ` Stephen Boyd
2016-03-01 19:24 ` Lina Iyer
2016-03-01 19:24 ` Lina Iyer
2016-02-12 20:50 ` [RFC v2 07/12] PM / cpu_domains: Add PM Domain governor for CPUs Lina Iyer
2016-02-12 20:50 ` Lina Iyer
2016-02-26 19:33 ` Stephen Boyd
2016-02-26 19:33 ` Stephen Boyd
2016-03-01 19:32 ` Lina Iyer
2016-03-01 19:32 ` Lina Iyer
2016-03-01 19:35 ` Stephen Boyd
2016-03-01 19:35 ` Stephen Boyd
2016-02-12 20:50 ` [RFC v2 08/12] Documentation / cpu_domains: Describe CPU PM domains setup and governor Lina Iyer
2016-02-12 20:50 ` Lina Iyer
2016-02-26 19:43 ` Stephen Boyd
2016-02-26 19:43 ` Stephen Boyd
2016-03-01 19:36 ` Lina Iyer
2016-03-01 19:36 ` Lina Iyer
2016-02-12 20:50 ` [RFC v2 09/12] drivers: firmware: psci: Allow OS Initiated suspend mode Lina Iyer
2016-02-12 20:50 ` Lina Iyer
2016-02-12 20:50 ` [RFC v2 10/12] ARM64: psci: Support cluster idle states for OS-Initiated Lina Iyer
2016-02-12 20:50 ` Lina Iyer
2016-02-12 20:50 ` [RFC v2 11/12] ARM64: dts: Add PSCI cpuidle support for MSM8916 Lina Iyer
2016-02-12 20:50 ` Lina Iyer
2016-02-12 20:50 ` [RFC v2 12/12] ARM64: dts: Define CPU power domain " Lina Iyer
2016-02-12 20:50 ` Lina Iyer
2016-02-26 19:50 ` Stephen Boyd
2016-02-26 19:50 ` Stephen Boyd
2016-03-01 19:41 ` Lina Iyer [this message]
2016-03-01 19:41 ` 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=20160301194149.GP1440@linaro.org \
--to=lina.iyer@linaro.org \
--cc=agross@codeaurora.org \
--cc=ahaslam@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=k.kozlowski@samsung.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=msivasub@codeaurora.org \
--cc=mtitinger@baylibre.com \
--cc=rjw@rjwysocki.net \
--cc=sboyd@codeaurora.org \
--cc=ulf.hansson@linaro.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.