Documentation/devicetree/bindings/rtc/sa1100-rtc.yaml
Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/rtc/sa1100-rtc.yaml
File Facts
- System
- Linux kernel
- Corpus path
Documentation/devicetree/bindings/rtc/sa1100-rtc.yaml- Extension
.yaml- Size
- 956 bytes
- Lines
- 58
- 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
%YAML 1.2
---
$id: http://devicetree.org/schemas/rtc/sa1100-rtc.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: Marvell Real Time Clock controller
allOf:
- $ref: rtc.yaml#
maintainers:
- Alessandro Zummo <a.zummo@towertech.it>
- Alexandre Belloni <alexandre.belloni@bootlin.com>
- Rob Herring <robh@kernel.org>
properties:
compatible:
enum:
- mrvl,sa1100-rtc
- mrvl,mmp-rtc
reg:
maxItems: 1
clocks:
maxItems: 1
resets:
maxItems: 1
interrupts:
minItems: 2
interrupt-names:
items:
- const: rtc 1Hz
- const: rtc alarm
required:
- compatible
- reg
- interrupts
- interrupt-names
additionalProperties: false
examples:
- |
rtc: rtc@d4010000 {
compatible = "mrvl,mmp-rtc";
reg = <0xd4010000 0x1000>;
interrupts = <5>, <6>;
interrupt-names = "rtc 1Hz", "rtc alarm";
};
...
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.