Re: [PATCH v3 2/2] clk: samsung: gs101: don't mark non-essential (UART) clocks critical

Marek Szyprowski
2024-07-10T14:35:18Z

On 10.07.2024 15:29, André Draszik wrote:
> The peric0_top1_ipclk_0 and peric0_top1_pclk_0 are the clocks going to
> peric0/uart_usi, with pclk being the bus clock. Without pclk running,
> any bus access will hang.
> Unfortunately, in commit d97b6c902a40 ("arm64: dts: exynos: gs101:
> update USI UART to use peric0 clocks") the gs101 DT ended up specifying
> an incorrect pclk in the respective node and instead the two clocks
> here were marked as critical.
>
> Since then, the DT has been updated to use the correct clock in
> commit 21e4e8807bfc ("arm64: dts: exynos: gs101: use correct clocks for
> usi_uart") and the driver here should be corrected and the work-around
> removed.
>
> Note that this commit has the side-effect of causing earlycon to stop
> to work sometime into the boot for two reasons:
> * peric0_top1_ipclk_0 requires its parent gout_cmu_peric0_ip to be
> running, but because earlycon doesn't deal with clocks that
> parent will be disabled when none of the other drivers that
> actually deal with clocks correctly require it to be running and
> the real serial driver (which does deal with clocks) hasn't taken
> over yet
> * hand-over between earlycon and serial driver appears to be
> fragile and clocks get enabled and disabled a few times, which
> also causes register access to hang while earlycon is still
> active
> (A wordier explanation can also be found in [1])
>
> Nonetheless we shouldn't keep these clocks running unconditionally just
> for earlycon. Clocks should be disabled where possible. If earlycon is
> required in the future, e.g. for debug, this commit can simply be
> reverted (locally!).
>
> Link: https://lore.kernel.org/all/d45de3b2bb6b48653842cf1f74e58889ed6783ae.camel@linaro.org/ [1]
> Fixes: 893f133a040b ("clk: samsung: gs101: add support for cmu_peric0")
> Signed-off-by: André Draszik <andre.draszik@linaro.org>
> Reviewed-by: Tudor Ambarus <tudor.ambarus@linaro.org>
> Reviewed-by: Sam Protsenko <semen.protsenko@linaro.org>

Frankly speaking I'm not sure that anyone will find this comment and do
local reverts before getting angry that earlycon doesn't work for his
device and wasting his time.

I think that it would be much better to check if earlycon is specified
in kernel's cmdline and if so, simply mark those problematic clocks
critical in this driver. Make this code hidden under
IS_ENABLED(CONFIG_SERIAL_EARLYCON) to avoid polluting release builds.
Any comments?

Best regards
--
Marek Szyprowski, PhD
Samsung R&D Institute Poland