Documentation/devicetree/bindings/timer/ezchip,nps400-timer.yaml

File Facts

System

Linux kernel

Corpus path

Documentation/devicetree/bindings/timer/ezchip,nps400-timer.yaml

Extension

.yaml

Size

777 bytes

Lines

46

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/ezchip,nps400-timer.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#

title: EZChip NPS400 Timers

maintainers:
  - Noam Camus <noamca@mellanox.com>

properties:
  compatible:
    enum:
      - ezchip,nps400-timer0
      - ezchip,nps400-timer1

  interrupts:
    maxItems: 1

  clocks:
    maxItems: 1

required:
  - compatible
  - clocks

additionalProperties: false

allOf:
  - if:
      properties:
        compatible:
          contains:
            const: ezchip,nps400-timer0
    then:
      required: [ interrupts ]

examples:
  - |
    timer {
        compatible = "ezchip,nps400-timer0";
        interrupts = <3>;
        clocks = <&sysclk>;
    };

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.