From: "sunyeal.hong" <sunyeal.hong@samsung.com>
To: "'Krzysztof Kozlowski'" <krzk@kernel.org>,
"'Rob Herring'" <robh@kernel.org>
Cc: "'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>,
"'Conor Dooley'" <conor+dt@kernel.org>,
<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 v4 1/4] dt-bindings: clock: add ExynosAuto v920 SoC CMU bindings
Date: Thu, 25 Jul 2024 16:14:53 +0900 [thread overview]
Message-ID: <041b01dade62$5861b2d0$09251870$@samsung.com> (raw)
In-Reply-To: <9647f1b5-9f34-42f0-b7b9-56ad9708855b@kernel.org>
Hello Krzysztof,
> -----Original Message-----
> From: Krzysztof Kozlowski <krzk@kernel.org>
> Sent: Thursday, July 25, 2024 3:41 PM
> To: sunyeal.hong <sunyeal.hong@samsung.com>; 'Rob Herring'
> <robh@kernel.org>
> Cc: '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>;
> 'Conor Dooley' <conor+dt@kernel.org>; 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 v4 1/4] dt-bindings: clock: add ExynosAuto v920 SoC
> CMU bindings
>
> On 25/07/2024 08:37, Krzysztof Kozlowski wrote:
> >> then:
> >> properties:
> >> clocks:
> >> items:
> >> - description: External reference clock (38.4 MHz)
> >> - description: CMU_MISC NOC clock (from CMU_MISC)
> >>
> >> clock-names:
> >> items:
> >> - const: oscclk
> >> - const: noc
> >>
> >> If there is anything I misunderstand, please guide me.
> >>
> >
> > You did not address my questions at all instead just copied again the
> > same. It is not how it works.
> >
> > I am not going to discuss like this.
>
> And in case it is still unclear - just look at your bindings and DTS.
> They say you have three clocks!
>
> Best regards,
> Krzysztof
>
Let me answer your questions first.
In the existing V4 patch, clock items were declared in if then for each block, so there was no problem.
If modified according to Rob's comment, problems may occur as the input clock is configured differently for each block.
I think it would be better to keep the bindings in v4 patch form like the existing exynos models.
Thanks for your comment.
Best regards,
Sunyeal
next prev parent reply other threads:[~2024-07-25 7:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240722223340epcas2p380657369f0b57c9e21f05f250066a711@epcas2p3.samsung.com>
2024-07-22 22:33 ` [PATCH v4 0/4] initial clock support for exynosauto v920 SoC Sunyeal Hong
2024-07-22 22:33 ` [PATCH v4 1/4] dt-bindings: clock: add ExynosAuto v920 SoC CMU bindings Sunyeal Hong
2024-07-23 20:57 ` Rob Herring
2024-07-25 1:24 ` sunyeal.hong
2024-07-25 3:03 ` sunyeal.hong
2024-07-25 6:21 ` Krzysztof Kozlowski
2024-07-25 6:35 ` sunyeal.hong
2024-07-25 6:37 ` Krzysztof Kozlowski
2024-07-25 6:40 ` Krzysztof Kozlowski
2024-07-25 7:14 ` sunyeal.hong [this message]
2024-07-25 7:31 ` Krzysztof Kozlowski
2024-07-25 7:50 ` sunyeal.hong
2024-07-25 7:56 ` Krzysztof Kozlowski
2024-07-29 2:48 ` sunyeal.hong
2024-07-24 10:12 ` Krzysztof Kozlowski
2024-07-25 1:25 ` sunyeal.hong
2024-07-22 22:33 ` [PATCH v4 2/4] arm64: dts: exynos: add initial CMU clock nodes in ExynosAuto v920 Sunyeal Hong
2024-07-24 10:13 ` Krzysztof Kozlowski
2024-07-25 1:28 ` sunyeal.hong
2024-07-24 11:17 ` Tudor Ambarus
2024-07-25 3:09 ` sunyeal.hong
2024-07-22 22:33 ` [PATCH v4 3/4] clk: samsung: clk-pll: Add support for pll_531x Sunyeal Hong
2024-07-22 22:33 ` [PATCH v4 4/4] clk: samsung: add top clock support for ExynosAuto v920 SoC Sunyeal Hong
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='041b01dade62$5861b2d0$09251870$@samsung.com' \
--to=sunyeal.hong@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 \
/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;
as well as URLs for NNTP newsgroup(s).