[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <25fde6ca-e1f4-4ca7-a534-efaae8a2a324@linaro.org>
Date: Tue, 20 Feb 2024 11:56:48 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Sam Protsenko <semen.protsenko@...aro.org>,
Sylwester Nawrocki <s.nawrocki@...sung.com>,
Chanwoo Choi <cw00.choi@...sung.com>
Cc: Alim Akhtar <alim.akhtar@...sung.com>,
Michael Turquette <mturquette@...libre.com>, Stephen Boyd
<sboyd@...nel.org>, Rob Herring <robh@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Tomasz Figa <tomasz.figa@...il.com>,
linux-samsung-soc@...r.kernel.org, linux-clk@...r.kernel.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 09/16] clk: samsung: Pass register layout type explicitly
to CLK_CPU()
On 16/02/2024 23:32, Sam Protsenko wrote:
> Make it more obvious which register layout should be used for a CPU
> clock. It prepares clk-cpu.c for adding new chips support.
>
> No functional change.
>
> Signed-off-by: Sam Protsenko <semen.protsenko@...aro.org>
> ---
> drivers/clk/samsung/clk-cpu.c | 2 +-
> drivers/clk/samsung/clk-cpu.h | 12 ++++++++++--
> drivers/clk/samsung/clk-exynos3250.c | 2 +-
> drivers/clk/samsung/clk-exynos4.c | 6 +++---
> drivers/clk/samsung/clk-exynos5250.c | 3 ++-
> drivers/clk/samsung/clk-exynos5420.c | 8 ++++----
> drivers/clk/samsung/clk-exynos5433.c | 8 ++++----
> drivers/clk/samsung/clk.h | 4 +++-
> 8 files changed, 28 insertions(+), 17 deletions(-)
>
> diff --git a/drivers/clk/samsung/clk-cpu.c b/drivers/clk/samsung/clk-cpu.c
> index 4c46416281a3..21998c89b96d 100644
> --- a/drivers/clk/samsung/clk-cpu.c
> +++ b/drivers/clk/samsung/clk-cpu.c
> @@ -464,7 +464,7 @@ static int __init exynos_register_cpu_clock(struct samsung_clk_provider *ctx,
> cpuclk->lock = &ctx->lock;
> cpuclk->flags = clk_data->flags;
> cpuclk->clk_nb.notifier_call = exynos_cpuclk_notifier_cb;
> - if (clk_data->flags & CLK_CPU_HAS_E5433_REGS_LAYOUT) {
> + if (clk_data->reg_layout == CPUCLK_LAYOUT_E5433) {
Why flags cannot work for it and we need one more property? The point of
flags is to customize the variant entirely. You basically split now
flags into flags A and flags B.
Best regards,
Krzysztof
Powered by blists - more mailing lists