From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Magnus Damm <magnus.damm@gmail.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-renesas-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 0/2] ARM/arm64: dts: renesas: Improve TMU interrupt descriptions
Date: Mon, 15 Jan 2024 14:46:38 +0100 [thread overview]
Message-ID: <cover.1705325654.git.geert+renesas@glider.be> (raw)
Hi all,
Some Timer Unit (TMU) instances with 3 channels support a fourth
interrupt: an input capture interrupt for the third channel.
The DT bindings are updated to reflect this in "PATCH] dt-bindings:
timer: renesas,tmu: Document input capture interrupt"[1], while this
patch series updates the DTS files.
I plan to queue this series in renesas-devel for v6.9, after acceptance
of the DT bindings update.
Thanks for your comments!
[1] https://lore.kernel.org/r/fb1e38c93e62221f94304edd980a2fb79c1f2995.1705325608.git.geert+renesas@glider.be
Geert Uytterhoeven (2):
ARM: dts: renesas: Improve TMU interrupt descriptions
arm64: dts: renesas: Improve TMU interrupt descriptions
arch/arm/boot/dts/renesas/r8a7740.dtsi | 2 ++
arch/arm/boot/dts/renesas/r8a7778.dtsi | 9 +++++++--
arch/arm/boot/dts/renesas/r8a7779.dtsi | 9 +++++++--
arch/arm64/boot/dts/renesas/r8a774a1.dtsi | 11 +++++++++--
arch/arm64/boot/dts/renesas/r8a774b1.dtsi | 11 +++++++++--
arch/arm64/boot/dts/renesas/r8a774c0.dtsi | 11 +++++++++--
arch/arm64/boot/dts/renesas/r8a774e1.dtsi | 11 +++++++++--
arch/arm64/boot/dts/renesas/r8a77951.dtsi | 11 +++++++++--
arch/arm64/boot/dts/renesas/r8a77960.dtsi | 11 +++++++++--
arch/arm64/boot/dts/renesas/r8a77961.dtsi | 11 +++++++++--
arch/arm64/boot/dts/renesas/r8a77965.dtsi | 11 +++++++++--
arch/arm64/boot/dts/renesas/r8a77970.dtsi | 11 +++++++++--
arch/arm64/boot/dts/renesas/r8a77980.dtsi | 17 +++++++++++++----
arch/arm64/boot/dts/renesas/r8a77990.dtsi | 11 +++++++++--
arch/arm64/boot/dts/renesas/r8a77995.dtsi | 11 +++++++++--
arch/arm64/boot/dts/renesas/r8a779a0.dtsi | 17 +++++++++++++----
arch/arm64/boot/dts/renesas/r8a779f0.dtsi | 17 +++++++++++++----
arch/arm64/boot/dts/renesas/r8a779g0.dtsi | 17 +++++++++++++----
18 files changed, 167 insertions(+), 42 deletions(-)
--
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-01-15 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 13:46 Geert Uytterhoeven [this message]
2024-01-15 13:46 ` [PATCH 1/2] ARM: dts: renesas: Improve TMU interrupt descriptions Geert Uytterhoeven
2024-01-15 13:46 ` [PATCH 2/2] arm64: " 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.1705325654.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=wsa+renesas@sang-engineering.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 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).