Documentation/devicetree/bindings/timer/jcore,pit.yaml
Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/timer/jcore,pit.yaml
File Facts
- System
- Linux kernel
- Corpus path
Documentation/devicetree/bindings/timer/jcore,pit.yaml- Extension
.yaml- Size
- 1091 bytes
- Lines
- 44
- 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
- No C-style include directives detected by the generator.
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/jcore,pit.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: J-Core Programmable Interval Timer and Clocksource
maintainers:
- Rich Felker <dalias@libc.org>
properties:
compatible:
const: jcore,pit
reg:
description:
Memory region(s) for timer/clocksource registers. For SMP, there should be
one region per cpu, indexed by the sequential, zero-based hardware cpu
number.
interrupts:
description:
An interrupt to assign for the timer. The actual pit core is integrated
with the aic and allows the timer interrupt assignment to be programmed by
software, but this property is required in order to reserve an interrupt
number that doesn't conflict with other devices.
maxItems: 1
required:
- compatible
- reg
- interrupts
additionalProperties: false
examples:
- |
timer@200 {
compatible = "jcore,pit";
reg = <0x200 0x30 0x500 0x30>;
interrupts = <0x48>;
};
Annotation
- 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.