greybus: timesync: reduce initial startup time

Currently we have a long initial delay when initiating the first operation
to synchronize the FrameTime. That made sense during development of the
feature since we did synchronization asynchronously and wanted to give some
grace time for new Interfaces to be added before initiating a new
synchronization. On the PM runtime resume path though we do a synchronous
restoration of FrameTime and in this case waiting for 1 second before
initiating the first operation is clearly wrong.

This patch reduces the initial operation time bringing the synchronous call
time down by 990 milliseconds.

Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>

diff --git a/drivers/staging/greybus/timesync.c b/drivers/staging/greybus/timesync.c
index ddbdf2beb48db280d9fd5c2aaf1b9cdfa26c4c96..23b209118f2a5dfced10412adb106d23d691d6d0 100644 (file)
--- a/drivers/staging/greybus/timesync.c
+++ b/drivers/staging/greybus/timesync.c
@@ -28,7 +28,7 @@
 #define GB_TIMESYNC_DEFAULT_OFFSET_US          1000
 
 /* Work queue timers long, short and SVC strobe timeout */
-#define GB_TIMESYNC_DELAYED_WORK_LONG          msecs_to_jiffies(1000)
+#define GB_TIMESYNC_DELAYED_WORK_LONG          msecs_to_jiffies(10)
 #define GB_TIMESYNC_DELAYED_WORK_SHORT         msecs_to_jiffies(1)
 #define GB_TIMESYNC_MAX_WAIT_SVC               msecs_to_jiffies(5000)
 #define GB_TIMESYNC_KTIME_UPDATE               msecs_to_jiffies(1000)