From: Scaria Kochidanadu <s-kochidanadu@ti.com>
To: Kendall Willis <k-willis@ti.com>, Nishanth Menon <nm@ti.com>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: <a-kaur@ti.com>, <s-tripathi1@ti.com>, <vishalm@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] arm64: dts: ti: k3-am625: add standby cpu idle state
Date: Mon, 7 Sep 2026 16:00:29 +0530 [thread overview]
Message-ID: <38c8d72a-50e5-44e2-a196-fb6b9f7530b0@ti.com> (raw)
In-Reply-To: <20260820-upstream-standby-v1-1-6a0553b9713d@ti.com>
On 21/08/26 00:58, Kendall Willis wrote:
> Allow the A53 cores to enter standby mode on the AM62x SoC.
> The standby idle state enables the CPU cores to enter WFI through the
> CPUIdle framework.
>
> Signed-off-by: Kendall Willis <k-willis@ti.com>
> ---
> arch/arm64/boot/dts/ti/k3-am625.dtsi | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-am625.dtsi b/arch/arm64/boot/dts/ti/k3-am625.dtsi
> index c249883a8a8d846aa21092c4c341fd443cfcec15..7ba339d5875926717896fc92fb2fa6d2b8d0026a 100644
> --- a/arch/arm64/boot/dts/ti/k3-am625.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-am625.dtsi
> @@ -51,6 +51,7 @@ cpu0: cpu@0 {
> operating-points-v2 = <&a53_opp_table>;
> clocks = <&k3_clks 135 0>;
> #cooling-cells = <2>;
> + cpu-idle-states = <&CPU_STANDBY>;
> };
>
> cpu1: cpu@1 {
> @@ -68,6 +69,7 @@ cpu1: cpu@1 {
> operating-points-v2 = <&a53_opp_table>;
> clocks = <&k3_clks 136 0>;
> #cooling-cells = <2>;
> + cpu-idle-states = <&CPU_STANDBY>;
> };
>
> cpu2: cpu@2 {
> @@ -85,6 +87,7 @@ cpu2: cpu@2 {
> operating-points-v2 = <&a53_opp_table>;
> clocks = <&k3_clks 137 0>;
> #cooling-cells = <2>;
> + cpu-idle-states = <&CPU_STANDBY>;
> };
>
> cpu3: cpu@3 {
> @@ -102,6 +105,20 @@ cpu3: cpu@3 {
> operating-points-v2 = <&a53_opp_table>;
> clocks = <&k3_clks 138 0>;
> #cooling-cells = <2>;
> + cpu-idle-states = <&CPU_STANDBY>;
> + };
> +
> + cpu_idle_states: idle-states {
> + entry-method = "psci";
> +
> + CPU_STANDBY: cpu-standby {
nit: The property ordering looks a bit unusual. Could we move the
'idle-state-name' immediately after 'compatible'
Scaria
> + compatible = "arm,idle-state";
> + entry-latency-us = <100>;
> + exit-latency-us = <50>;
> + idle-state-name = "standby";
> + min-residency-us = <500>;
> + arm,psci-suspend-param = <0x00000001>;
> + };
> };
> };
>
>
next prev parent reply other threads:[~2026-09-07 10:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 19:28 [PATCH 0/3] arm64: dts: ti: add standby cpu idle state to AM62 SoCs Kendall Willis
2026-08-20 19:28 ` [PATCH 1/3] arm64: dts: ti: k3-am625: add standby cpu idle state Kendall Willis
2026-09-07 10:30 ` Scaria Kochidanadu [this message]
2026-09-09 11:22 ` Nishanth Menon
2026-09-11 16:02 ` Kendall Willis
2026-09-11 19:24 ` Nishanth Menon
2026-08-20 19:28 ` [PATCH 2/3] arm64: dts: ti: k3-am62a7: " Kendall Willis
2026-08-20 19:28 ` [PATCH 3/3] arm64: dts: ti: k3-am62p5: " Kendall Willis
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=38c8d72a-50e5-44e2-a196-fb6b9f7530b0@ti.com \
--to=s-kochidanadu@ti.com \
--cc=a-kaur@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=k-willis@ti.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=s-tripathi1@ti.com \
--cc=vigneshr@ti.com \
--cc=vishalm@ti.com \
/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