Documentation/devicetree/bindings/embedded-controller/traverse,ten64-controller.yaml

File Facts

System

Linux kernel

Corpus path

Documentation/devicetree/bindings/embedded-controller/traverse,ten64-controller.yaml

Extension

.yaml

Size

867 bytes

Lines

41

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/embedded-controller/traverse,ten64-controller.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#

title: Traverse Ten64 board microcontroller

maintainers:
  - Mathew McBride <matt@traverse.com.au>

description: |
  The board microcontroller on the Ten64 board family is responsible for
  management of power sources on the board, as well as signalling the SoC
  to power on and reset.

properties:
  compatible:
    const: traverse,ten64-controller

  reg:
    const: 0x7e

required:
  - compatible
  - reg

additionalProperties: false

examples:
  - |
    i2c {
        #address-cells = <1>;
        #size-cells = <0>;

        board-controller@7e {
            compatible = "traverse,ten64-controller";
            reg = <0x7e>;
        };
    };

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.