From: Konrad Dybcio <konradybcio@kernel.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH] arm64: dts: qcom: sa8775p: add CPU idle states
Date: Thu, 5 Sep 2024 14:34:39 +0200 [thread overview]
Message-ID: <06895dff-bdbf-4dfd-8f00-ee850297ec12@kernel.org> (raw)
In-Reply-To: <20240807-sa8775p-idle-states-v1-1-f2b5fcdfa0b0@linaro.org>
On 7.08.2024 3:31 PM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>
> Add CPU idle-state nodes and power-domains to the .dtsi for SA8775P.
>
> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> ---
[...]
> + CLUSTER_0_PD: power-domain-cluster0 {
> + #power-domain-cells = <0>;
> + power-domains = <&CLUSTER_2_PD>;
> + domain-idle-states = <&CLUSTER_SLEEP_GOLD>;
> + };
> +
> + CLUSTER_1_PD: power-domain-cluster1 {
> + #power-domain-cells = <0>;
> + power-domains = <&CLUSTER_2_PD>;
> + domain-idle-states = <&CLUSTER_SLEEP_GOLD>;
> + };
> +
> + CLUSTER_2_PD: power-domain-cluster2 {
> + #power-domain-cells = <0>;
> + domain-idle-states = <&CLUSTER_SLEEP_APSS_RSC_PC>;
> + };
[...]
You want to define a SYSTEM_PD that's parent to the CLUSTER domains, like
in x1e, then APSS_RSC_PC would be an idle state of that pd
Konrad
prev parent reply other threads:[~2024-09-05 12:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 13:31 [PATCH] arm64: dts: qcom: sa8775p: add CPU idle states Bartosz Golaszewski
2024-08-15 20:40 ` Bjorn Andersson
2024-09-05 12:34 ` Konrad Dybcio [this message]
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=06895dff-bdbf-4dfd-8f00-ee850297ec12@kernel.org \
--to=konradybcio@kernel.org \
--cc=andersson@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox