From: "André Draszik" <andre.draszik@linaro.org>
To: Peter Griffin <peter.griffin@linaro.org>,
Tudor Ambarus <tudor.ambarus@linaro.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Krzysztof Kozlowski <krzk@kernel.org>
Cc: William Mcvicker <willmcvicker@google.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@android.com
Subject: Re: [PATCH v3] soc: samsung: exynos-pmu: Enable CPU Idle for gs101
Date: Thu, 03 Jul 2025 12:01:13 +0100 [thread overview]
Message-ID: <53a214b4039872ce7584a2ae6e688fcef0c86d7e.camel@linaro.org> (raw)
In-Reply-To: <20250627-gs101-cpuidle-v3-1-0200452dfe60@linaro.org>
More small comments. Sorry for the drip feed, just trying to understand
things...
On Fri, 2025-06-27 at 14:08 +0100, Peter Griffin wrote:
> [...]
>
> +static int gs101_cpu_pm_notify_callback(struct notifier_block *self,
> + unsigned long action, void *v)
> +{
> + switch (action) {
> + case CPU_PM_ENTER:
> + /*
> + * Ignore CPU_PM_ENTER event in reboot or
> + * suspend sequence.
> + */
> +
> + if (atomic_read(&pmu_context->sys_suspended) ||
> + atomic_read(&pmu_context->sys_rebooting))
> + return NOTIFY_OK;
> +
> + return gs101_cpu_pmu_offline();
> +
> + break;
break is not needed after return, and generally there should be an empty
line before the next case statement.
> + case CPU_PM_EXIT:
Should this also handle CPU_PM_ENTER_FAILED in the same way to bring
the CPU back up in case of failures?
> +
> + if (atomic_read(&pmu_context->sys_rebooting))
> + return NOTIFY_OK;
> +
> + return gs101_cpu_pmu_online();
> +
> + break;
No break needed.
Cheers,
Andre'
next prev parent reply other threads:[~2025-07-03 11:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 13:08 Peter Griffin
2025-07-03 10:12 ` André Draszik
2025-07-03 10:19 ` Krzysztof Kozlowski
2025-07-08 15:51 ` Peter Griffin
2025-07-08 15:50 ` Peter Griffin
2025-07-03 11:01 ` André Draszik [this message]
2025-07-09 10:04 ` Peter Griffin
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=53a214b4039872ce7584a2ae6e688fcef0c86d7e.camel@linaro.org \
--to=andre.draszik@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=kernel-team@android.com \
--cc=krzk@kernel.org \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®