From: Bjorn Andersson <andersson@kernel.org>
To: Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Navya Malempati <navya.malempati@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Remove gold/silver_cpu_sleep idle states for lemans and monaco
Date: Wed, 8 Jul 2026 09:56:51 -0500 [thread overview]
Message-ID: <178352261580.2235436.15511501261812237159.b4-ty@kernel.org> (raw)
In-Reply-To: <20260522-ml_cpuidle-v1-0-fd311cf33fb4@oss.qualcomm.com>
On Fri, 22 May 2026 16:40:12 +0530, Navya Malempati wrote:
> Firmware supports both CPU power collapse and CPU PLL/rail power collapse
> idle states. However, CPU power collapse mode is often not utilized in
> favor of performance. Remove CPU power collapse modes for lemans and
> monaco as well aligning with SM8350/SM8450/SM8550/SM8650.
>
Applied, thanks!
[1/2] arm64: dts: qcom: monaco: Remove the little/big_cpu_sleep_0 idle states
commit: 00dd037fc31452962eba38cdb46feafb0b70d96e
[2/2] arm64: dts: qcom: lemans: Remove the gold_cpu_sleep idle state
commit: f212c011af87e65c5147bfd61d786d681be91d40
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2026-07-08 14:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 11:10 [PATCH 0/2] Remove gold/silver_cpu_sleep idle states for lemans and monaco Navya Malempati
2026-05-22 11:10 ` [PATCH 1/2] arm64: dts: qcom: monaco: Remove the little/big_cpu_sleep_0 idle states Navya Malempati
2026-06-05 10:04 ` Maulik Shah (mkshah)
2026-06-07 19:24 ` Dmitry Baryshkov
2026-06-08 8:23 ` Navya Malempati
2026-05-22 11:10 ` [PATCH 2/2] arm64: dts: qcom: lemans: Remove the gold_cpu_sleep idle state Navya Malempati
2026-06-05 10:05 ` Maulik Shah (mkshah)
2026-07-08 14:56 ` Bjorn Andersson [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=178352261580.2235436.15511501261812237159.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=navya.malempati@oss.qualcomm.com \
--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