From: Marc Zyngier <maz@kernel.org>
To: Florian Fainelli <florian.fainelli@broadcom.com>
Cc: Daniel Drake <dan@reactivated.net>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
bcm-kernel-feedback-list@broadcom.com,
devicetree@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, m.szyprowski@samsung.com,
andrea.porta@suse.com
Subject: Re: [PATCH] arm64: dts: broadcom: bcm2712: Remove non-functional EL2 virtual timer
Date: Fri, 10 Jul 2026 09:17:36 +0100 [thread overview]
Message-ID: <87se5r5kdb.wl-maz@kernel.org> (raw)
In-Reply-To: <f25e0d6e-941e-416f-8c80-2c48e1b90498@broadcom.com>
On Thu, 09 Jul 2026 14:18:58 +0100,
Florian Fainelli <florian.fainelli@broadcom.com> wrote:
>
>
>
> On 7/6/2026 11:49 PM, Daniel Drake wrote:
> > Hi Florian,
> >
> > On 21/06/2026 21:03, Florian Fainelli wrote:
> >> We have an internal bug tracker item pertaining exactly to the
> >> virtual timer interrupt connection however it affected a sister
> >> chip (77122) and not 2712 AFAICT, now checking with the design team
> >> whether the same happened on 2712.
> > Did you receive any update on this for 2712?
>
> Not yet, no.
I've posted this:
https://lore.kernel.org/all/20260710080958.491620-1-maz@kernel.org/
as we can't leave users with non-functional HW much longer.
M.
--
Jazz isn't dead. It just smells funny.
next prev parent reply other threads:[~2026-07-10 8:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260619204921eucas1p1c4a9fe8e8a41f552d4637dee2b26f4e4@eucas1p1.samsung.com>
2026-06-19 20:48 ` [PATCH] arm64: dts: broadcom: bcm2712: Remove non-functional EL2 virtual timer Daniel Drake
2026-06-19 21:04 ` Marek Szyprowski
2026-06-20 8:49 ` Marc Zyngier
2026-06-21 20:03 ` Florian Fainelli
2026-06-21 20:58 ` Daniel Drake
2026-06-22 6:20 ` Marek Szyprowski
2026-07-06 21:49 ` Daniel Drake
2026-07-09 13:18 ` Florian Fainelli
2026-07-10 8:17 ` Marc Zyngier [this message]
2026-07-13 16:15 ` Florian Fainelli
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=87se5r5kdb.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=andrea.porta@suse.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=dan@reactivated.net \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=m.szyprowski@samsung.com \
--cc=robh@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.