From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
"André Draszik" <andre.draszik@linaro.org>,
"Tudor Ambarus" <tudor.ambarus@linaro.org>,
"Alim Akhtar" <alim.akhtar@samsung.com>,
"Peter Griffin" <peter.griffin@linaro.org>
Cc: William Mcvicker <willmcvicker@google.com>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@android.com, sudeep.holla@arm.com
Subject: Re: [PATCH v7] soc: samsung: exynos-pmu: Enable CPU Idle for gs101
Date: Wed, 23 Jul 2025 11:00:41 +0200 [thread overview]
Message-ID: <bca15900-da2d-4384-a79a-ee630fd7cee2@kernel.org> (raw)
In-Reply-To: <175308588382.28993.16370211179082448125.b4-ty@linaro.org>
On 21/07/2025 10:18, Krzysztof Kozlowski wrote:
>
> On Thu, 17 Jul 2025 17:22:36 +0100, Peter Griffin wrote:
>> Register cpu pm notifiers for gs101 which call the
>> gs101_cpu_pmu_online/offline callbacks which in turn program the ACPM
>> C2 hint. This hint is required to actually enter the C2 idle state in
>> addition to the PSCI calls due to limitations in the el3mon/ACPM firmware.
>>
>> A couple of corner cases are handled, namely when the system is rebooting
>> or suspending we ignore the request. Additionally the request is ignored if
>> the CPU is in CPU hot plug. Some common code is refactored so that it can
>> be called from both the CPU hot plug callbacks and CPU PM notifier taking
>> into account that CPU PM notifiers are called with IRQs disabled whereas
>> CPU hotplug callbacks are not.
>>
>> [...]
>
> Applied, thanks!
>
> [1/1] soc: samsung: exynos-pmu: Enable CPU Idle for gs101
> (no commit info)
>
... and dropped, because I missed the part it is not bisectable. This
cannot go the same cycle.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-07-23 9:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 16:22 [PATCH v7] soc: samsung: exynos-pmu: Enable CPU Idle for gs101 Peter Griffin
2025-07-21 8:18 ` Krzysztof Kozlowski
2025-07-23 9:00 ` Krzysztof Kozlowski [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=bca15900-da2d-4384-a79a-ee630fd7cee2@kernel.org \
--to=krzk@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=andre.draszik@linaro.org \
--cc=kernel-team@android.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=sudeep.holla@arm.com \
--cc=tudor.ambarus@linaro.org \
--cc=willmcvicker@google.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 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.