From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Magnus Damm <magnus.damm@gmail.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Biju Das <biju.das.jz@bp.renesas.com>,
Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Marc Zyngier <maz@kernel.org>,
linux-renesas-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 0/9] dts: renesas: Add missing hypervisor virtual timer IRQs and interrupt-names
Date: Thu, 20 Jun 2024 15:57:30 +0200 [thread overview]
Message-ID: <cover.1718890849.git.geert+renesas@glider.be> (raw)
Hi all,
Support for the hypervisor virtual timer interrupt of the ARM
architected timer was only added, together with interrupt-names support,
in commits a6cf39fbe133857a ("dt-bindings: timer: arm,arch_timer: Add
interrupt-names support") and 86332e9e3477af8f ("arm64: arch_timer:
Implement support for interrupt-names") in v5.13.
This patch series enhances device nodes that represent ARM architected
timers on Renesas SoCs, by (a) adding the missing hypervisor virtual
timer interrupts, and (b) adding interrupt-names properties for clarity.
I plan to queue this in renesas-devel for v6.11.
Thanks for your comments!
Geert Uytterhoeven (9):
arm64: dts: renesas: r8a779a0: Add missing hypervisor virtual timer
IRQ
arm64: dts: renesas: r8a779f0: Add missing hypervisor virtual timer
IRQ
arm64: dts: renesas: r8a779g0: Add missing hypervisor virtual timer
IRQ
arm64: dts: renesas: r9a07g043u: Add missing hypervisor virtual timer
IRQ
arm64: dts: renesas: r9a07g044: Add missing hypervisor virtual timer
IRQ
arm64: dts: renesas: r9a07g054: Add missing hypervisor virtual timer
IRQ
arm64: dts: renesas: r9a08g045: Add missing hypervisor virtual timer
IRQ
ARM: dts: renesas: Add interrupt-names to arch timer nodes
arm64: dts: renesas: Add interrupt-names to arch timer nodes
arch/arm/boot/dts/renesas/r8a73a4.dtsi | 1 +
arch/arm/boot/dts/renesas/r8a7742.dtsi | 1 +
arch/arm/boot/dts/renesas/r8a7743.dtsi | 1 +
arch/arm/boot/dts/renesas/r8a7744.dtsi | 1 +
arch/arm/boot/dts/renesas/r8a7745.dtsi | 1 +
arch/arm/boot/dts/renesas/r8a77470.dtsi | 1 +
arch/arm/boot/dts/renesas/r8a7790.dtsi | 1 +
arch/arm/boot/dts/renesas/r8a7791.dtsi | 1 +
arch/arm/boot/dts/renesas/r8a7792.dtsi | 1 +
arch/arm/boot/dts/renesas/r8a7793.dtsi | 1 +
arch/arm/boot/dts/renesas/r8a7794.dtsi | 1 +
arch/arm/boot/dts/renesas/r9a06g032.dtsi | 1 +
arch/arm64/boot/dts/renesas/r8a774a1.dtsi | 1 +
arch/arm64/boot/dts/renesas/r8a774b1.dtsi | 1 +
arch/arm64/boot/dts/renesas/r8a774c0.dtsi | 1 +
arch/arm64/boot/dts/renesas/r8a774e1.dtsi | 1 +
arch/arm64/boot/dts/renesas/r8a77951.dtsi | 1 +
arch/arm64/boot/dts/renesas/r8a77960.dtsi | 1 +
arch/arm64/boot/dts/renesas/r8a77961.dtsi | 1 +
arch/arm64/boot/dts/renesas/r8a77965.dtsi | 1 +
arch/arm64/boot/dts/renesas/r8a77970.dtsi | 1 +
arch/arm64/boot/dts/renesas/r8a77980.dtsi | 1 +
arch/arm64/boot/dts/renesas/r8a77990.dtsi | 1 +
arch/arm64/boot/dts/renesas/r8a77995.dtsi | 1 +
arch/arm64/boot/dts/renesas/r8a779a0.dtsi | 5 ++++-
arch/arm64/boot/dts/renesas/r8a779f0.dtsi | 5 ++++-
arch/arm64/boot/dts/renesas/r8a779g0.dtsi | 5 ++++-
arch/arm64/boot/dts/renesas/r8a779h0.dtsi | 2 ++
arch/arm64/boot/dts/renesas/r9a07g043u.dtsi | 5 ++++-
arch/arm64/boot/dts/renesas/r9a07g044.dtsi | 5 ++++-
arch/arm64/boot/dts/renesas/r9a07g054.dtsi | 5 ++++-
arch/arm64/boot/dts/renesas/r9a08g045.dtsi | 5 ++++-
arch/arm64/boot/dts/renesas/r9a09g011.dtsi | 1 +
33 files changed, 55 insertions(+), 7 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
next reply other threads:[~2024-06-20 13:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 13:57 Geert Uytterhoeven [this message]
2024-06-20 13:57 ` [PATCH 1/9] arm64: dts: renesas: r8a779a0: Add missing hypervisor virtual timer IRQ Geert Uytterhoeven
2024-06-20 13:57 ` [PATCH 2/9] arm64: dts: renesas: r8a779f0: " Geert Uytterhoeven
2024-06-20 13:57 ` [PATCH 3/9] arm64: dts: renesas: r8a779g0: " Geert Uytterhoeven
2024-06-20 13:57 ` [PATCH 4/9] arm64: dts: renesas: r9a07g043u: " Geert Uytterhoeven
2024-06-27 12:13 ` Lad, Prabhakar
2024-06-20 13:57 ` [PATCH 5/9] arm64: dts: renesas: r9a07g044: " Geert Uytterhoeven
2024-06-27 12:14 ` Lad, Prabhakar
2024-06-20 13:57 ` [PATCH 6/9] arm64: dts: renesas: r9a07g054: " Geert Uytterhoeven
2024-06-27 12:16 ` Lad, Prabhakar
2024-06-20 13:57 ` [PATCH 7/9] arm64: dts: renesas: r9a08g045: " Geert Uytterhoeven
2024-06-24 4:56 ` claudiu beznea
2024-06-20 13:57 ` [PATCH 8/9] ARM: dts: renesas: Add interrupt-names to arch timer nodes Geert Uytterhoeven
2024-06-20 13:57 ` [PATCH 9/9] 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.1718890849.git.geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=biju.das.jz@bp.renesas.com \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=yoshihiro.shimoda.uh@renesas.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).