From: Conor Dooley <conor@kernel.org>
To: Joel Stanley <joel@jms.id.au>
Cc: Paul Walmsley <pjw@kernel.org>, Rob Herring <robh@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Anup Patel <anup@brainfault.org>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
Nicholas Piggin <npiggin@gmail.com>,
Michael Ellerman <mpe@kernel.org>,
Drew Fustini <fustini@kernel.org>,
linux-riscv@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 4/7] dt-bindings: timer: Add RISC-V ACLINT bindings
Date: Thu, 4 Jun 2026 16:21:42 +0100 [thread overview]
Message-ID: <20260604-phonics-venue-48a4f241aed0@spud> (raw)
In-Reply-To: <CACPK8Xf=Ec16jR+J399Pqi=O=2GgFjkZOPFo0AKaAA+58R6-gQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3086 bytes --]
On Fri, Jun 05, 2026 at 12:09:06AM +0930, Joel Stanley wrote:
> On Wed, 3 Jun 2026 at 18:53, Conor Dooley <conor@kernel.org> wrote:
> >
> > On Wed, Jun 03, 2026 at 05:12:16PM +0930, Joel Stanley wrote:
> > > Document the bindings for the RISC-V ACLINT.
> > >
> > > Signed-off-by: Drew Fustini <fustini@kernel.org>
> > > Signed-off-by: Joel Stanley <joel@jms.id.au>
> > > ---
> > > MAINTAINERS | 1 +
> > > .../bindings/timer/riscv,aclint-mtimer.yaml | 52 +++++++++++++++++++
> > > 2 files changed, 53 insertions(+)
> > > create mode 100644 Documentation/devicetree/bindings/timer/riscv,aclint-mtimer.yaml
> > >
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > index 2fb1c75afd16..43dd9873bbc5 100644
> > > --- a/MAINTAINERS
> > > +++ b/MAINTAINERS
> > > @@ -23005,6 +23005,7 @@ M: Joel Stanley <jms@oss.tenstorrent.com>
> > > L: linux-riscv@lists.infradead.org
> > > S: Maintained
> > > T: git https://github.com/tenstorrent/linux.git
> > > +F: Documentation/devicetree/bindings/timer/riscv,aclint-mtimer.yaml
> > > F: Documentation/devicetree/bindings/clock/tenstorrent,atlantis-prcm-rcpu.yaml
> > > F: Documentation/devicetree/bindings/riscv/tenstorrent.yaml
> > > F: arch/riscv/boot/dts/tenstorrent/
> > > diff --git a/Documentation/devicetree/bindings/timer/riscv,aclint-mtimer.yaml b/Documentation/devicetree/bindings/timer/riscv,aclint-mtimer.yaml
> > > new file mode 100644
> > > index 000000000000..192ff3fcf79f
> > > --- /dev/null
> > > +++ b/Documentation/devicetree/bindings/timer/riscv,aclint-mtimer.yaml
> > > @@ -0,0 +1,52 @@
> > > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > > +%YAML 1.2
> > > +---
> > > +$id: http://devicetree.org/schemas/timer/riscv,aclint-mtimer.yaml#
> > > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > > +
> > > +title: RISC-V Advanced Core Local Interruptor (ACLINT)
> > > +
> > > +maintainers:
> > > + - Joel Stanley <jms@oss.tenstorrent.com>
> > > +
> > > +description:
> > > + This RISC-V ACLINT specification defines a set of memory mapped devices which
> > > + provide inter-processor interrupts (IPI) and timer functionalities for each
> > > + HART on a multi-HART RISC-V platform. The specification can be found at
> > > + https://github.com/riscvarchive/riscv-aclint/
> >
> > This is a draft specification, so having a "riscv,aclint-mtimer"
> > compatible is not appropriate. Ordinarily I would say that you should be
> > able to do this once frozen, but this spec is archived and unlikely to
> > have that happen.
>
> I've reworked the binding to reference the privileged spec, which is
> ratified and has a section on the timer registers:
>
> https://docs.riscv.org/reference/isa/priv/machine.html#3-1-2-1-machine-timer-mtime-and-mtimecmp-registers
>
> I'll post a v2 now for review.
To be clear, the problem isn't referencing the draft spec (that is what
you implemented after all). It's the "riscv,aclint-mtimer" compatible
that's the problem.
Cheers,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-06-04 15:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 7:42 [PATCH 0/7] riscv: dts: tenstorrent: Add Atlantis platform Joel Stanley
2026-06-03 7:42 ` [PATCH 1/7] dt-bindings: aplic: Add Tenstorrent Atlantis compatible Joel Stanley
2026-06-03 7:47 ` Anup Patel
2026-06-03 16:19 ` Conor Dooley
2026-06-03 7:42 ` [PATCH 2/7] dt-bindings: imsics: " Joel Stanley
2026-06-03 7:48 ` Anup Patel
2026-06-03 16:18 ` Conor Dooley
2026-06-03 7:42 ` [PATCH 3/7] dt-bindings: riscv: cpus: Add Tenstorrent Ascalon Joel Stanley
2026-06-03 16:18 ` Conor Dooley
2026-06-03 7:42 ` [PATCH 4/7] dt-bindings: timer: Add RISC-V ACLINT bindings Joel Stanley
2026-06-03 7:50 ` Anup Patel
2026-06-03 7:55 ` sashiko-bot
2026-06-03 9:23 ` Conor Dooley
2026-06-04 14:39 ` Joel Stanley
2026-06-04 15:21 ` Conor Dooley [this message]
2026-06-03 7:42 ` [PATCH 5/7] dt-bindings: riscv: add Smrnmi extension description Joel Stanley
2026-06-03 16:17 ` Conor Dooley
2026-06-03 7:42 ` [PATCH 6/7] dt-bindings: riscv: Add Tenstorrent Atlantis platform Joel Stanley
2026-06-03 16:17 ` Conor Dooley
2026-06-03 19:37 ` Drew Fustini
2026-06-03 7:42 ` [PATCH 7/7] riscv: dts: tenstorrent: Add " Joel Stanley
2026-06-03 8:04 ` sashiko-bot
2026-06-03 9:16 ` Conor Dooley
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=20260604-phonics-venue-48a4f241aed0@spud \
--to=conor@kernel.org \
--cc=alex@ghiti.fr \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fustini@kernel.org \
--cc=joel@jms.id.au \
--cc=linux-riscv@lists.infradead.org \
--cc=mpe@kernel.org \
--cc=npiggin@gmail.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox