[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <53a214b4039872ce7584a2ae6e688fcef0c86d7e.camel@linaro.org>
Date: Thu, 03 Jul 2025 12:01:13 +0100
From: André Draszik <andre.draszik@...aro.org>
To: Peter Griffin <peter.griffin@...aro.org>, Tudor Ambarus
<tudor.ambarus@...aro.org>, Alim Akhtar <alim.akhtar@...sung.com>,
Krzysztof Kozlowski <krzk@...nel.org>
Cc: William Mcvicker <willmcvicker@...gle.com>, Krzysztof Kozlowski
<krzysztof.kozlowski@...aro.org>, linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org,
kernel-team@...roid.com
Subject: Re: [PATCH v3] soc: samsung: exynos-pmu: Enable CPU Idle for gs101
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'
Powered by blists - more mailing lists