From: Geert Uytterhoeven <geert+renesas@glider.be>
To: "Magnus Damm" <magnus.damm@gmail.com>,
"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Cc: linux-renesas-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 0/3] ARM: dts: renesas: Add more TMU support
Date: Tue, 19 Mar 2024 17:29:04 +0100 [thread overview]
Message-ID: <cover.1710864964.git.geert+renesas@glider.be> (raw)
Hi all,
This patch series adds device nodes for the Timer Units (TMU) on the
R-Mobile APE6 SoC, and on various SoCs from the RZ/G1 and R-Car Gen2
family.
All TMU instances have been tested successfully using [1] on R-Mobile
APE6 (APE6EVM), and on R-Car H2 (Lager) and M2-W (Koelsch), except for
TMU3 on M2-W, which consistently fails the CLOCK_REALTIME test (why?).
Still to be queued in renesas-devel for v6.10?
Thanks for your comments!
[1] https://elinux.org/R-Car/Tests:timers
Geert Uytterhoeven (3):
ARM: dts: renesas: r8a73a4: Add TMU nodes
ARM: dts: renesas: rzg1: Add TMU nodes
ARM: dts: renesas: rcar-gen2: Add TMU nodes
arch/arm/boot/dts/renesas/r8a73a4.dtsi | 37 ++++++++++++++
arch/arm/boot/dts/renesas/r8a7742.dtsi | 58 ++++++++++++++++++++++
arch/arm/boot/dts/renesas/r8a7743.dtsi | 58 ++++++++++++++++++++++
arch/arm/boot/dts/renesas/r8a7744.dtsi | 58 ++++++++++++++++++++++
arch/arm/boot/dts/renesas/r8a7745.dtsi | 58 ++++++++++++++++++++++
arch/arm/boot/dts/renesas/r8a77470.dtsi | 44 +++++++++++++++++
arch/arm/boot/dts/renesas/r8a7790.dtsi | 58 ++++++++++++++++++++++
arch/arm/boot/dts/renesas/r8a7791.dtsi | 58 ++++++++++++++++++++++
arch/arm/boot/dts/renesas/r8a7792.dtsi | 59 +++++++++++++++++++++++
arch/arm/boot/dts/renesas/r8a7793.dtsi | 58 ++++++++++++++++++++++
arch/arm/boot/dts/renesas/r8a7794.dtsi | 58 ++++++++++++++++++++++
include/dt-bindings/clock/r8a73a4-clock.h | 4 ++
12 files changed, 608 insertions(+)
--
2.34.1
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2024-03-19 16:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 16:29 Geert Uytterhoeven [this message]
2024-03-19 16:29 ` [PATCH 1/3] ARM: dts: renesas: r8a73a4: Add TMU nodes Geert Uytterhoeven
2024-03-19 22:42 ` Niklas Söderlund
2024-03-20 9:33 ` Krzysztof Kozlowski
2024-03-20 10:06 ` Geert Uytterhoeven
2024-03-19 16:29 ` [PATCH 2/3] ARM: dts: renesas: rzg1: " Geert Uytterhoeven
2024-03-19 16:29 ` [PATCH 3/3] ARM: dts: renesas: rcar-gen2: " Geert Uytterhoeven
2024-03-19 22:55 ` Niklas Söderlund
2024-03-20 7:31 ` Wolfram Sang
2024-03-20 7:08 ` [PATCH 0/3] ARM: dts: renesas: Add more TMU support Wolfram Sang
2024-03-20 8:03 ` Geert Uytterhoeven
2024-03-20 8:34 ` Wolfram Sang
2024-03-20 10:09 ` Geert Uytterhoeven
2024-03-21 10:17 ` Geert Uytterhoeven
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=cover.1710864964.git.geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=niklas.soderlund+renesas@ragnatech.se \
/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).