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