| Tom Rini | 53633a8 | 2024-02-29 12:33:36 -0500 | [diff] [blame] | 1 | # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) |
| 2 | %YAML 1.2 |
| 3 | --- |
| 4 | $id: http://devicetree.org/schemas/timestamp/hardware-timestamps-common.yaml# |
| 5 | $schema: http://devicetree.org/meta-schemas/core.yaml# |
| 6 | |
| 7 | title: Hardware timestamp providers |
| 8 | |
| 9 | maintainers: |
| 10 | - Dipen Patel <dipenp@nvidia.com> |
| 11 | |
| 12 | description: |
| 13 | Some devices/SoCs have hardware timestamp engines (HTE) which can use |
| 14 | hardware means to timestamp entity in realtime. The entity could be anything |
| 15 | from GPIOs, IRQs, Bus and so on. The hardware timestamp engine present |
| 16 | itself as a provider with the bindings described in this document. |
| 17 | |
| 18 | properties: |
| 19 | $nodename: |
| 20 | pattern: "^timestamp(@.*|-([0-9]|[1-9][0-9]+))?$" |
| 21 | |
| 22 | "#timestamp-cells": |
| 23 | description: |
| 24 | Number of cells in a HTE specifier. |
| 25 | |
| 26 | required: |
| 27 | - "#timestamp-cells" |
| 28 | |
| 29 | additionalProperties: true |