Documentation/devicetree/bindings/timer/renesas,cmt.yaml
Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/timer/renesas,cmt.yaml
File Facts
- System
- Linux kernel
- Corpus path
Documentation/devicetree/bindings/timer/renesas,cmt.yaml- Extension
.yaml- Size
- 8196 bytes
- Lines
- 207
- Domain
- Support Tooling And Documentation
- Bucket
- Documentation
- Inferred role
- Support Tooling And Documentation: configuration, schema, or hardware description
- Status
- atlas-only
Why This File Exists
Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
Dependency Surface
dt-bindings/clock/r8a7790-cpg-mssr.hdt-bindings/interrupt-controller/arm-gic.hdt-bindings/power/r8a7790-sysc.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
%YAML 1.2
---
$id: http://devicetree.org/schemas/timer/renesas,cmt.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: Renesas Compare Match Timer (CMT)
maintainers:
- Geert Uytterhoeven <geert+renesas@glider.be>
- Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
description:
The CMT is a multi-channel 16/32/48-bit timer/counter with configurable clock
inputs and programmable compare match.
Channels share hardware resources but their counter and compare match values
are independent. A particular CMT instance can implement only a subset of the
channels supported by the CMT model. Channel indices represent the hardware
position of the channel in the CMT and don't match the channel numbers in the
datasheets.
properties:
compatible:
oneOf:
- items:
- enum:
- renesas,r8a7740-cmt0 # 32-bit CMT0 on R-Mobile A1
- renesas,r8a7740-cmt1 # 48-bit CMT1 on R-Mobile A1
- renesas,r8a7740-cmt2 # 32-bit CMT2 on R-Mobile A1
- renesas,r8a7740-cmt3 # 32-bit CMT3 on R-Mobile A1
- renesas,r8a7740-cmt4 # 32-bit CMT4 on R-Mobile A1
- renesas,sh73a0-cmt0 # 32-bit CMT0 on SH-Mobile AG5
- renesas,sh73a0-cmt1 # 48-bit CMT1 on SH-Mobile AG5
- renesas,sh73a0-cmt2 # 32-bit CMT2 on SH-Mobile AG5
- renesas,sh73a0-cmt3 # 32-bit CMT3 on SH-Mobile AG5
- renesas,sh73a0-cmt4 # 32-bit CMT4 on SH-Mobile AG5
- items:
- enum:
- renesas,r8a73a4-cmt0 # 32-bit CMT0 on R-Mobile APE6
- renesas,r8a7742-cmt0 # 32-bit CMT0 on RZ/G1H
- renesas,r8a7743-cmt0 # 32-bit CMT0 on RZ/G1M
- renesas,r8a7744-cmt0 # 32-bit CMT0 on RZ/G1N
- renesas,r8a7745-cmt0 # 32-bit CMT0 on RZ/G1E
- renesas,r8a77470-cmt0 # 32-bit CMT0 on RZ/G1C
- renesas,r8a7790-cmt0 # 32-bit CMT0 on R-Car H2
- renesas,r8a7791-cmt0 # 32-bit CMT0 on R-Car M2-W
- renesas,r8a7792-cmt0 # 32-bit CMT0 on R-Car V2H
- renesas,r8a7793-cmt0 # 32-bit CMT0 on R-Car M2-N
- renesas,r8a7794-cmt0 # 32-bit CMT0 on R-Car E2
- const: renesas,rcar-gen2-cmt0 # 32-bit CMT0 on R-Mobile APE6, R-Car Gen2 and RZ/G1
- items:
- enum:
- renesas,r8a73a4-cmt1 # 48-bit CMT1 on R-Mobile APE6
- renesas,r8a7742-cmt1 # 48-bit CMT1 on RZ/G1H
- renesas,r8a7743-cmt1 # 48-bit CMT1 on RZ/G1M
- renesas,r8a7744-cmt1 # 48-bit CMT1 on RZ/G1N
- renesas,r8a7745-cmt1 # 48-bit CMT1 on RZ/G1E
- renesas,r8a77470-cmt1 # 48-bit CMT1 on RZ/G1C
- renesas,r8a7790-cmt1 # 48-bit CMT1 on R-Car H2
- renesas,r8a7791-cmt1 # 48-bit CMT1 on R-Car M2-W
- renesas,r8a7792-cmt1 # 48-bit CMT1 on R-Car V2H
- renesas,r8a7793-cmt1 # 48-bit CMT1 on R-Car M2-N
- renesas,r8a7794-cmt1 # 48-bit CMT1 on R-Car E2
- const: renesas,rcar-gen2-cmt1 # 48-bit CMT1 on R-Mobile APE6, R-Car Gen2 and RZ/G1
- items:
- enum:
Annotation
- Immediate include surface: `dt-bindings/clock/r8a7790-cpg-mssr.h`, `dt-bindings/interrupt-controller/arm-gic.h`, `dt-bindings/power/r8a7790-sysc.h`.
- Atlas domain: Support Tooling And Documentation / Documentation.
- Implementation status: atlas-only.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.