From 7172871ef3a711375661e22d4d8ed2c7f8c0c509 Mon Sep 17 00:00:00 2001 From: Sheetal Tigadoli Date: Thu, 30 Jan 2025 17:55:33 +0000 Subject: [PATCH] devicetree:bindings:nvpps: update doc to include Thor update nvpps documentation to include Thor based platforms Bug 5082436 Signed-off-by: Sheetal Tigadoli Change-Id: I4d26dab5d5eb40df449c819912a3143360a97f51 Reviewed-on: https://git-master.nvidia.com/r/c/linux-nv-oot/+/3293986 (cherry picked from commit 8dd44d031ce394923f4e02a07befcb162eedd714) Reviewed-on: https://git-master.nvidia.com/r/c/linux-nv-oot/+/3293842 Reviewed-by: Amlan Kundu GVS: buildbot_gerritrpt --- Documentation/devicetree/bindings/nvpps/nvpps.txt | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Documentation/devicetree/bindings/nvpps/nvpps.txt b/Documentation/devicetree/bindings/nvpps/nvpps.txt index c4efc4ec..0b1cbec9 100644 --- a/Documentation/devicetree/bindings/nvpps/nvpps.txt +++ b/Documentation/devicetree/bindings/nvpps/nvpps.txt @@ -28,12 +28,15 @@ Optional properties: or locking TSC time with PTP time domain. The value is a 8bit hexa-decimal value. If unspecified, NvPPS driver uses 0x70 as default value + This field is not used for Thor based platforms - ptp_tsc_lock_threshold: specifies the threshold value which is used by HW to determine if the TSC PTP sync/Lock is lost. The lock is deemed to be lost if the HW determined absolute diff between PTP & TSC time exceed this value. The value is a 16bit hexa-decimal value. The minimum value(0x1F) supported correspond to 1us and max value(0xFFFF) supported correspond to approx 2.1ms. If unspecified, NvPPS driver uses 0x26C(corresponding to 20us) by default + On Thor based platforms, Minimum value(1) supported correspond to 1ns and + Max value(16777215) correspond to approx 16.77ms - ptp_tsc_sync_dis: boolean flag to indicate if nvpps should disable PTP TSC sync logic. The default behaviour is to keep PTP TSC sync logic enabled. - reg: specifies start address and registers count details of TSC module. It is only applicable for Orin.