From: Kendall Willis <k-willis@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: Scaria Kochidanadu <s-kochidanadu@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>, <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: Fri, 11 Sep 2026 11:02:57 -0500 [thread overview]
Message-ID: <20260911160257.xgq3xe76iijq2bxw@uda0506412> (raw)
In-Reply-To: <20260909112211.2zckbx2omnrjhkwp@scarily>
Hi Nishanth,
On 06:22-20260909, Nishanth Menon wrote:
> On 16:00-20260907, Scaria Kochidanadu wrote:
> >
> > 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.
>
> A very basic question: Default Idle in kernel *is* WFI. So, what kind of
> savings are we seeing by explicitly enabling a cpuidle state that goes
> to WFI and more importantly why?
>
There is no additional power savings from the added cpuidle state.
Adding the cpuidle state allows users to use cpuidle to see see stats
about WFI from userspace.
Best,
Kendall
next prev parent reply other threads:[~2026-09-11 16:03 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
2026-09-09 11:22 ` Nishanth Menon
2026-09-11 16:02 ` Kendall Willis [this message]
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=20260911160257.xgq3xe76iijq2bxw@uda0506412 \
--to=k-willis@ti.com \
--cc=a-kaur@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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-kochidanadu@ti.com \
--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;
as well as URLs for NNTP newsgroup(s).