Documentation/devicetree/bindings/arm/ti/ti,keystone.yaml

File Facts

System

Linux kernel

Corpus path

Documentation/devicetree/bindings/arm/ti/ti,keystone.yaml

Extension

.yaml

Size

1019 bytes

Lines

43

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

title: TI Keystone Platforms

maintainers:
  - Nishanth Menon <nm@ti.com>
  - Santosh Shilimkar <ssantosh@kernel.org>

properties:
  compatible:
    oneOf:
      - description: K2G
        items:
          - enum:
              - ti,k2g-evm
              - ti,k2g-ice
          - const: ti,k2g
          - const: ti,keystone
      - description: Keystone 2 Edison
        items:
          - enum:
              - ti,k2e-evm
          - const: ti,k2e
          - const: ti,keystone
      - description: Keystone 2 Lamarr
        items:
          - enum:
              - ti,k2l-evm
          - const: ti,k2l
          - const: ti,keystone
      - description: Keystone 2 Hawking/Kepler
        items:
          - enum:
              - ti,k2hk-evm
          - const: ti,k2hk
          - const: ti,keystone

additionalProperties: true

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.