From: 손신 <shin.son@samsung.com>
To: "'Krzysztof Kozlowski'" <krzk@kernel.org>,
"'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 cpucl0 clock support
Date: Wed, 23 Apr 2025 09:59:23 +0900 [thread overview]
Message-ID: <003701dbb3ea$f42360c0$dc6a2240$@samsung.com> (raw)
In-Reply-To: <6de6030a-af26-4fda-8d49-fa8ac65a672f@kernel.org>
Hello Krzysztof Kozlowski,
> -----Original Message-----
> From: Krzysztof Kozlowski [mailto:krzk@kernel.org]
> Sent: Tuesday, April 22, 2025 4:59 PM
> 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 cpucl0 clock
> support
>
> On 18/04/2025 08:14, Shin Son wrote:
> > Register compatible and cmu_info data to support clock CMU_CPUCL0,
> > this provides clock for CPUCL0_SWTICH/DBG/CLUSTER.
> >
>
> Explain why this is needed as clk of declare, instead of platform driver.
>
>
>
> Best regards,
> Krzysztof
CPUCL0 refers CPU Cluster 0.
Since the CPU clocks need to be available as early as possible, I used CLK_OF_DECLARE instead of a platform driver.
I'll update the commit message and add a comment in the code to clarify this.
Best regards,
Shin Son
next prev parent reply other threads:[~2025-04-23 1:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250418061515epcas2p1ddd9ec01dd5de8b238c77dcef14d745a@epcas2p1.samsung.com>
2025-04-18 6:14 ` [PATCH 0/3] add CPUCL0 clock support for exynosauto v920 SoC Shin Son
2025-04-18 6:14 ` [PATCH 1/3] dt-bindings: clock: exynosautov920: add cpucl0 clock definitions Shin Son
2025-04-22 7:54 ` Krzysztof Kozlowski
2025-04-23 0:45 ` 손신
2025-04-18 6:14 ` [PATCH 2/3] clk: samsung: exynosautov920: add cpucl0 clock support Shin Son
2025-04-22 7:59 ` Krzysztof Kozlowski
2025-04-23 0:59 ` 손신 [this message]
2025-04-18 6:15 ` [PATCH 3/3] arm64: dts: exynosautov920: add cpucl0 clock DT nodes Shin Son
2025-04-22 8:00 ` Krzysztof Kozlowski
2025-04-23 1:05 ` 손신
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='003701dbb3ea$f42360c0$dc6a2240$@samsung.com' \
--to=shin.son@samsung.com \
--cc=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.