Linux clock framework development
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Shin Son <shin.son@samsung.com>,
	Sylwester Nawrocki <s.nawrocki@samsung.com>,
	Chanwoo Choi <cw00.choi@samsung.com>,
	Alim Akhtar <alim.akhtar@samsung.com>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Sunyeal Hong <sunyeal.hong@samsung.com>
Cc: linux-samsung-soc@vger.kernel.org, linux-clk@vger.kernel.org,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] clk: samsung: exynosautov920: add cpucl1/2 clock support
Date: Mon, 28 Apr 2025 11:14:33 +0200	[thread overview]
Message-ID: <a3438b8b-0fd2-454f-a539-39aa7cfcd57b@kernel.org> (raw)
In-Reply-To: <20250428084721.3832664-3-shin.son@samsung.com>

On 28/04/2025 10:47, Shin Son wrote:
> Register compatible and cmu_info data to support clock CPUCL1/2
> (CPU Cluster 1 and CPU Cluster 2),
> these provide clock for CPUCL1/2_SWTICH/CLUSTER.
> 
> These clocks are required early during boot for the CPUs,
> so they are declared using CLK_OF_DECLARE instead of being registered
> through a platform driver.
> 
> Signed-off-by: Shin Son <shin.son@samsung.com>
> ---
>  drivers/clk/samsung/clk-exynosautov920.c | 208 ++++++++++++++++++++++-
>  1 file changed, 207 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/clk/samsung/clk-exynosautov920.c b/drivers/clk/samsung/clk-exynosautov920.c
> index 8021e0912e50..f8168eed4a66 100644
> --- a/drivers/clk/samsung/clk-exynosautov920.c
> +++ b/drivers/clk/samsung/clk-exynosautov920.c
> @@ -18,7 +18,9 @@
>  
>  /* NOTE: Must be equal to the last clock ID increased by one */
>  #define CLKS_NR_TOP			(DOUT_CLKCMU_TAA_NOC + 1)
> -#define CLKS_NR_CPUCL0			(CLK_DOUT_CLUSTER0_PERIPHCLK + 1)
> +#define CLKS_NR_CPUCL0			(CLK_DOUT_CPUCL0_NOCP + 1)


You just added that line a week ago and it is already incorrect? Then it
needs patch on its own explaining what are you fixing.


Best regards,
Krzysztof

  reply	other threads:[~2025-04-28  9:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20250428084728epcas2p486ddfccc41bfba9830bde544b6c292e3@epcas2p4.samsung.com>
2025-04-28  8:47 ` [PATCH 0/3] add CPUCL1/2 clock support for exynosauto v920 SoC Shin Son
2025-04-28  8:47   ` [PATCH 1/3] dt-bindings: clock: exynosautov920: add cpucl1/2 clock definitions Shin Son
2025-04-28  9:13     ` Krzysztof Kozlowski
2025-04-28 10:41       ` 손신
2025-04-28  8:47   ` [PATCH 2/3] clk: samsung: exynosautov920: add cpucl1/2 clock support Shin Son
2025-04-28  9:14     ` Krzysztof Kozlowski [this message]
2025-04-28 10:47       ` 손신
2025-04-28  8:47   ` [PATCH 3/3] arm64: dts: exynosautov920: add cpucl1/2 clock DT nodes Shin Son

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=a3438b8b-0fd2-454f-a539-39aa7cfcd57b@kernel.org \
    --to=krzk@kernel.org \
    --cc=alim.akhtar@samsung.com \
    --cc=conor+dt@kernel.org \
    --cc=cw00.choi@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=robh@kernel.org \
    --cc=s.nawrocki@samsung.com \
    --cc=sboyd@kernel.org \
    --cc=shin.son@samsung.com \
    --cc=sunyeal.hong@samsung.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