From: Ivaylo Ivanov <ivo.ivanov.ivanov1@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Andi Shyti <andi.shyti@kernel.org>,
Mark Brown <broonie@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>
Cc: linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/5] arm64: dts: exynos8895: Add cmu, mct, serial_0/1 and spi_0/1
Date: Wed, 23 Oct 2024 12:17:29 +0300 [thread overview]
Message-ID: <20241023091734.538682-1-ivo.ivanov.ivanov1@gmail.com> (raw)
Hey folks,
This patchset adds device tree nodes for multiple clock management unit
blocks, MCT, SPI and UART for Exynos8895.
Exynos8895 uses USIv1 for most of its serial buses, except a few that
have been implemented in this series. Support for USIv1 and HSI2C will
be added in the future.
This patchset is dependent on [1] and [2], which add driver support for
CMU and UART.
[1] https://lore.kernel.org/all/20241023090136.537395-1-ivo.ivanov.ivanov1@gmail.com/
[2] https://lore.kernel.org/all/20241023090902.538040-1-ivo.ivanov.ivanov1@gmail.com/
Changes in v2:
- Add r-b from Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
- Change clock-names according to the v2 changes for clk bindings
Ivaylo Ivanov (5):
dt-bindings: timer: exynos4210-mct: Add samsung,exynos8895-mct
compatible
arm64: dts: exynos8895: Add clock management unit nodes
arm64: dts: exynos8895: Add Multi Core Timer (MCT) node
arm64: dts: exynos8895: Add serial_0/1 nodes
arm64: dts: exynos8895: Add spi_0/1 nodes
.../timer/samsung,exynos4210-mct.yaml | 2 +
arch/arm64/boot/dts/exynos/exynos8895.dtsi | 161 ++++++++++++++++++
2 files changed, 163 insertions(+)
--
2.43.0
next reply other threads:[~2024-10-23 9:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 9:17 Ivaylo Ivanov [this message]
2024-10-23 9:17 ` [PATCH v2 1/5] dt-bindings: timer: exynos4210-mct: Add samsung,exynos8895-mct compatible Ivaylo Ivanov
2024-10-23 9:17 ` [PATCH v2 2/5] arm64: dts: exynos8895: Add clock management unit nodes Ivaylo Ivanov
2024-10-23 9:17 ` [PATCH v2 3/5] arm64: dts: exynos8895: Add Multi Core Timer (MCT) node Ivaylo Ivanov
2024-10-23 9:17 ` [PATCH v2 4/5] arm64: dts: exynos8895: Add serial_0/1 nodes Ivaylo Ivanov
2024-12-02 8:53 ` (subset) " Krzysztof Kozlowski
2024-10-23 9:17 ` [PATCH v2 5/5] arm64: dts: exynos8895: Add spi_0/1 nodes Ivaylo Ivanov
2024-10-23 11:59 ` [PATCH v2 0/5] arm64: dts: exynos8895: Add cmu, mct, serial_0/1 and spi_0/1 Ivaylo Ivanov
2024-10-26 11:53 ` Krzysztof Kozlowski
2024-10-26 11:59 ` Ivaylo Ivanov
2024-10-26 12:02 ` Krzysztof Kozlowski
2024-10-26 12:12 ` Krzysztof Kozlowski
2024-10-26 12:18 ` Ivaylo Ivanov
2024-11-07 16:02 ` Ivaylo Ivanov
2024-11-08 11:11 ` Krzysztof Kozlowski
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=20241023091734.538682-1-ivo.ivanov.ivanov1@gmail.com \
--to=ivo.ivanov.ivanov1@gmail.com \
--cc=alim.akhtar@samsung.com \
--cc=andi.shyti@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
/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).