From: "Gary Guo" <gary@garyguo.net>
To: "Marc Zyngier" <maz@kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Cc: "John" <therealgraysky@proton.me>,
"Daniel Drake" <dan@reactivated.net>,
"Marek Szyprowski" <m.szyprowski@samsung.com>,
"Florian Fainelli" <florian.fainelli@broadcom.com>,
"Daniel Lezcano" <daniel.lezcano@linaro.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Mark Rutland" <mark.rutland@arm.com>
Subject: Re: [PATCH] clocksource/drivers/arm_arch_timer: Workaround bcm2712 broken EL2 virtual timer
Date: Tue, 21 Jul 2026 20:03:42 +0100 [thread overview]
Message-ID: <DK4HE3FGL1IC.1ISUZNYRIVVQL@garyguo.net> (raw)
In-Reply-To: <20260710080958.491620-1-maz@kernel.org>
On Fri Jul 10, 2026 at 9:09 AM BST, Marc Zyngier wrote:
> It appears that the bcm2712 SoC found in the relatively popular
> RPi5 has a broken EL2 virtual timer.
>
> We do not know the reason why the timer isn't working (the timer
> is ticking, but the interrupt never fires), and the SoC vendor
> doesn't communicate on the reason why this isn't working, leaving
> users and maintainers in the dark.
>
> Paper over the issue by detecting the broken HW, falling back to
> the physical timer instead, and let the user know about it.
> Also taint the kernel as the machine is definitely not compliant
> with the spec, and we don't know what else is wrong with it.
>
> Reported-by: John <therealgraysky@proton.me>
> Reported-by: Daniel Drake <dan@reactivated.net>
> Reported-by: Marek Szyprowski <m.szyprowski@samsung.com>
> Signed-off-by: Marc Zyngier <maz@kernel.org>
> Cc: Florian Fainelli <florian.fainelli@broadcom.com>
> Cc: Daniel Lezcano <daniel.lezcano@linaro.org>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Mark Rutland <mark.rutland@arm.com>
Tested on my RPi 5 and this does make it boot again
Tested-by: Gary Guo <gary@garyguo.net>
Best,
Gary
> ---
> drivers/clocksource/arm_arch_timer.c | 24 +++++++++++++++++++++++-
> 1 file changed, 23 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/clocksource/arm_arch_timer.c b/drivers/clocksource/arm_arch_timer.c
> index 4adf756423de9..7b4a98df6962b 100644
> --- a/drivers/clocksource/arm_arch_timer.c
> +++ b/drivers/clocksource/arm_arch_timer.c
> @@ -1090,6 +1090,27 @@ static int __init arch_timer_common_init(void)
> return arch_timer_arch_init();
> }
>
> +static bool __init has_broken_el2_vtimer(void)
> +{
> + /*
> + * SoCs described here have been found to be broken, though no
> + * explanation has been volunteered by the vendor. Let the user know
> + * we're papering over the vendor's lack of communication.
> + */
> + static const char * const broken_el2_vtimer[] __initconst = {
> + "brcm,bcm2712",
> + NULL
> + };
> +
> + if (of_machine_compatible_match(broken_el2_vtimer)) {
> + add_taint(TAINT_CPU_OUT_OF_SPEC, LOCKDEP_STILL_OK);
> + pr_warn_once(HW_ERR "Known broken EL2 virtual timer, ignoring it\n");
> + return true;
> + }
> +
> + return false;
> +}
> +
> /**
> * arch_timer_select_ppi() - Select suitable PPI for the current system.
> *
> @@ -1115,7 +1136,8 @@ static int __init arch_timer_common_init(void)
> static enum arch_timer_ppi_nr __init arch_timer_select_ppi(void)
> {
> if (is_kernel_in_hyp_mode()) {
> - if (arch_timer_ppi[ARCH_TIMER_HYP_VIRT_PPI])
> + if (arch_timer_ppi[ARCH_TIMER_HYP_VIRT_PPI] &&
> + !has_broken_el2_vtimer())
> return ARCH_TIMER_HYP_VIRT_PPI;
>
> pr_warn_once(FW_BUG "VHE-capable CPU without EL2 virtual timer interrupt\n");
next prev parent reply other threads:[~2026-07-21 19:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 8:09 [PATCH] clocksource/drivers/arm_arch_timer: Workaround bcm2712 broken EL2 virtual timer Marc Zyngier
2026-07-13 16:15 ` Florian Fainelli
2026-07-13 20:23 ` Marc Zyngier
2026-07-13 22:38 ` Florian Fainelli
2026-07-21 19:03 ` Gary Guo [this message]
2026-07-22 14:14 ` Jon Hunter
2026-07-22 20:22 ` Marc Zyngier
2026-07-23 9:24 ` Jon Hunter
2026-07-23 9:58 ` Marc Zyngier
2026-07-23 10:22 ` Jon Hunter
2026-07-23 10:46 ` Marc Zyngier
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=DK4HE3FGL1IC.1ISUZNYRIVVQL@garyguo.net \
--to=gary@garyguo.net \
--cc=dan@reactivated.net \
--cc=daniel.lezcano@linaro.org \
--cc=florian.fainelli@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=tglx@linutronix.de \
--cc=therealgraysky@proton.me \
/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