Documentation/devicetree/bindings/timestamp/hardware-timestamps-common.yaml

Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/timestamp/hardware-timestamps-common.yaml

File Facts

System: Linux kernel
Corpus path: Documentation/devicetree/bindings/timestamp/hardware-timestamps-common.yaml
Extension: .yaml
Size: 823 bytes
Lines: 30
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/timestamp/hardware-timestamps-common.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#

title: Hardware timestamp providers

maintainers:
  - Dipen Patel <dipenp@nvidia.com>

description:
  Some devices/SoCs have hardware timestamp engines (HTE) which can use
  hardware means to timestamp entity in realtime. The entity could be anything
  from GPIOs, IRQs, Bus and so on. The hardware timestamp engine present
  itself as a provider with the bindings described in this document.

properties:
  $nodename:
    pattern: "^timestamp(@.*|-([0-9]|[1-9][0-9]+))?$"

  "#timestamp-cells":
    description:
      Number of cells in a HTE specifier.

required:
  - "#timestamp-cells"

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.