From: Krzysztof Kozlowski <krzk@kernel.org>
To: Ivaylo Ivanov <ivo.ivanov.ivanov1@gmail.com>,
Krzysztof Kozlowski <krzk+dt@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>
Cc: linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org,
"open list:COMMON CLK FRAMEWORK" <linux-clk@vger.kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/3] dt-bindings: clock: add Exynos2200 SoC
Date: Sun, 23 Feb 2025 11:16:55 +0100 [thread overview]
Message-ID: <38b2f870-9965-4fd7-b9f1-dde8cbeed41e@kernel.org> (raw)
In-Reply-To: <20250215115433.161091-2-ivo.ivanov.ivanov1@gmail.com>
On 15/02/2025 12:54, Ivaylo Ivanov wrote:
> Provide dt-schema documentation for Exynos2200 SoC clock controller.
> Add device tree clock binding definitions for the following CMU blocks:
> - CMU_ALIVE
> - CMU_CMGP
> - CMU_HSI0
> - CMU_PERIC0/1/2
> - CMU_PERIS
> - CMU_TOP
> - CMU_UFS
> - CMU_VTS
>
> Signed-off-by: Ivaylo Ivanov <ivo.ivanov.ivanov1@gmail.com>
> ---
> .../clock/samsung,exynos2200-clock.yaml | 247 ++++++++++
> .../dt-bindings/clock/samsung,exynos2200.h | 431 ++++++++++++++++++
Let's unify the naming from now on to match compatible:
samsung,exynos2200-cmu.yaml
amsung,exynos2200-cmu.h
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-02-23 10:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-15 11:54 [PATCH v1 0/3] clk: samsung: introduce Exynos2200 clock driver Ivaylo Ivanov
2025-02-15 11:54 ` [PATCH v1 1/3] dt-bindings: clock: add Exynos2200 SoC Ivaylo Ivanov
2025-02-23 10:16 ` Krzysztof Kozlowski [this message]
2025-02-15 11:54 ` [PATCH v1 2/3] clk: samsung: clk-pll: add support for pll_4311 Ivaylo Ivanov
2025-02-15 11:54 ` [PATCH v1 3/3] clk: samsung: introduce Exynos2200 clock driver Ivaylo Ivanov
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=38b2f870-9965-4fd7-b9f1-dde8cbeed41e@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=ivo.ivanov.ivanov1@gmail.com \
--cc=krzk+dt@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
all inboxes | Powered by JetHome®