summaryrefslogtreecommitdiffstats
path: root/dts/Bindings/timestamp/hardware-timestamps-common.yaml
diff options
context:
space:
mode:
Diffstat (limited to 'dts/Bindings/timestamp/hardware-timestamps-common.yaml')
-rw-r--r--dts/Bindings/timestamp/hardware-timestamps-common.yaml29
1 files changed, 29 insertions, 0 deletions
diff --git a/dts/Bindings/timestamp/hardware-timestamps-common.yaml b/dts/Bindings/timestamp/hardware-timestamps-common.yaml
new file mode 100644
index 0000000000..fd6a7b51f5
--- /dev/null
+++ b/dts/Bindings/timestamp/hardware-timestamps-common.yaml
@@ -0,0 +1,29 @@
+# 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-9a-f])?$"
+
+ "#timestamp-cells":
+ description:
+ Number of cells in a HTE specifier.
+
+required:
+ - "#timestamp-cells"
+
+additionalProperties: true