Documentation/devicetree/bindings/interrupt-controller/ezchip,nps400-ic.yaml

File Facts

System

Linux kernel

Corpus path

Documentation/devicetree/bindings/interrupt-controller/ezchip,nps400-ic.yaml

Extension

.yaml

Size

651 bytes

Lines

35

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

title: EZchip NPS Interrupt Controller

maintainers:
  - Noam Camus <noamc@ezchip.com>

properties:
  compatible:
    const: ezchip,nps400-ic

  interrupt-controller: true

  '#interrupt-cells':
    const: 1

required:
  - compatible
  - interrupt-controller
  - '#interrupt-cells'

additionalProperties: false

examples:
  - |
    interrupt-controller {
        compatible = "ezchip,nps400-ic";
        interrupt-controller;
        #interrupt-cells = <1>;
    };

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.