linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "tip-bot2 for Ben Zong-You Xie" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: "Ben Zong-You Xie" <ben717@andestech.com>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Ingo Molnar <mingo@kernel.org>,
	Conor Dooley <conor.dooley@microchip.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: timers/clocksource] dt-bindings: timer: Add Andes machine timer
Date: Fri, 25 Jul 2025 10:31:45 -0000	[thread overview]
Message-ID: <175343950587.1420.13476286643465202699.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20250711133025.2192404-6-ben717@andestech.com>

The following commit has been merged into the timers/clocksource branch of tip:

Commit-ID:     1294b89e0d11966231ce237ed2ef0f24bf2cff84
Gitweb:        https://git.kernel.org/tip/1294b89e0d11966231ce237ed2ef0f24bf2cff84
Author:        Ben Zong-You Xie <ben717@andestech.com>
AuthorDate:    Fri, 11 Jul 2025 21:30:21 +08:00
Committer:     Ingo Molnar <mingo@kernel.org>
CommitterDate: Fri, 25 Jul 2025 12:04:51 +02:00

dt-bindings: timer: Add Andes machine timer

Add the DT binding documentation for Andes machine timer.

The RISC-V architecture defines a machine timer that provides a real-time
counter and generates timer interrupts. Andes machiner timer (PLMT0) is
the implementation of the machine timer, and it contains memory-mapped
registers (mtime and mtimecmp). This device supports up to 32 cores.

Signed-off-by: Ben Zong-You Xie <ben717@andestech.com>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Acked-by: Conor Dooley <conor.dooley@microchip.com>
Link: https://lore.kernel.org/r/20250711133025.2192404-6-ben717@andestech.com
---
 Documentation/devicetree/bindings/timer/andestech,plmt0.yaml | 53 +++++++-
 1 file changed, 53 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/timer/andestech,plmt0.yaml

diff --git a/Documentation/devicetree/bindings/timer/andestech,plmt0.yaml b/Documentation/devicetree/bindings/timer/andestech,plmt0.yaml
new file mode 100644
index 0000000..90b6120
--- /dev/null
+++ b/Documentation/devicetree/bindings/timer/andestech,plmt0.yaml
@@ -0,0 +1,53 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/timer/andestech,plmt0.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Andes machine-level timer
+
+description:
+  The Andes machine-level timer device (PLMT0) provides machine-level timer
+  functionality for a set of HARTs on a RISC-V platform. It has a single
+  fixed-frequency monotonic time counter (MTIME) register and a time compare
+  register (MTIMECMP) for each HART connected to the PLMT0. A timer interrupt is
+  generated if MTIME >= MTIMECMP.
+
+maintainers:
+  - Ben Zong-You Xie <ben717@andestech.com>
+
+properties:
+  compatible:
+    items:
+      - enum:
+          - andestech,qilai-plmt
+      - const: andestech,plmt0
+
+  reg:
+    maxItems: 1
+
+  interrupts-extended:
+    minItems: 1
+    maxItems: 32
+    description:
+      Specifies which harts are connected to the PLMT0. Each item must points
+      to a riscv,cpu-intc node, which has a riscv cpu node as parent. The
+      PLMT0 supports 1 hart up to 32 harts.
+
+additionalProperties: false
+
+required:
+  - compatible
+  - reg
+  - interrupts-extended
+
+examples:
+  - |
+    interrupt-controller@100000 {
+      compatible = "andestech,qilai-plmt", "andestech,plmt0";
+      reg = <0x100000 0x100000>;
+      interrupts-extended = <&cpu0intc 7>,
+                            <&cpu1intc 7>,
+                            <&cpu2intc 7>,
+                            <&cpu3intc 7>;
+    };

  parent reply	other threads:[~2025-07-25 10:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-11 13:30 [PATCH v2 0/9] add Voyager board support Ben Zong-You Xie
2025-07-11 13:30 ` [PATCH v2 1/9] riscv: add Andes SoC family Kconfig support Ben Zong-You Xie
2025-07-11 13:30 ` [PATCH v2 2/9] dt-bindings: riscv: add Andes QiLai SoC and the Voyager board bindings Ben Zong-You Xie
2025-07-11 13:30 ` [PATCH v2 3/9] dt-bindings: interrupt-controller: add Andes QiLai PLIC Ben Zong-You Xie
2025-07-11 13:30 ` [PATCH v2 4/9] dt-bindings: interrupt-controller: add Andes machine-level software interrupt controller Ben Zong-You Xie
2025-07-11 13:30 ` [PATCH v2 5/9] dt-bindings: timer: add Andes machine timer Ben Zong-You Xie
2025-07-14 16:18   ` Daniel Lezcano
2025-07-23  7:17   ` [tip: timers/clocksource] " tip-bot2 for Ben Zong-You Xie
2025-07-25 10:31   ` tip-bot2 for Ben Zong-You Xie [this message]
2025-07-11 13:30 ` [PATCH v2 6/9] riscv: dts: andes: add QiLai SoC device tree Ben Zong-You Xie
2025-07-11 13:30 ` [PATCH v2 7/9] riscv: dts: andes: add Voyager board " Ben Zong-You Xie
2025-07-11 13:30 ` [PATCH v2 8/9] riscv: defconfig: enable Andes SoC Ben Zong-You Xie
2025-07-11 13:30 ` [PATCH v2 9/9] MAINTAINERS: Add entry for " Ben Zong-You Xie
2025-08-10 21:12 ` [PATCH v2 0/9] add Voyager board support patchwork-bot+linux-riscv

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=175343950587.1420.13476286643465202699.tip-bot2@tip-bot2 \
    --to=tip-bot2@linutronix.de \
    --cc=ben717@andestech.com \
    --cc=conor.dooley@microchip.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=x86@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;
as well as URLs for NNTP newsgroup(s).