From 10a24b7c0911d63c7342dfb860e939221b4a9465 Mon Sep 17 00:00:00 2001 From: Bryan O'Donoghue Date: Wed, 20 Jul 2016 19:31:18 +0100 Subject: greybus: timesync: probe shouldn't complete until FrameTime sync does Currently the probe() function contains the asynchronous() variant of FrameTime synchronization. This patch converts to the synchronous() version of synchronization. This is required for two reasons first a probe() cannot reasonably be considered to be complete without successfully completing a time synchronization for Interfaces that care about that sync. Secondly scheduling the operation asynchronously means its possible the PM-runtime suspend() path can execute before the async timesync operation completes. For both reasons we want to run synchronization - synchronously. Signed-off-by: Bryan O'Donoghue Reviewed-by: Viresh Kumar Signed-off-by: Greg Kroah-Hartman --- drivers/staging/greybus/core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'drivers/staging') diff --git a/drivers/staging/greybus/core.c b/drivers/staging/greybus/core.c index 2c94bbb..8c77d6c 100644 --- a/drivers/staging/greybus/core.c +++ b/drivers/staging/greybus/core.c @@ -219,7 +219,7 @@ static int greybus_probe(struct device *dev) return retval; } - gb_timesync_schedule_asynchronous(bundle->intf); + gb_timesync_schedule_synchronous(bundle->intf); pm_runtime_put(&bundle->intf->dev); -- cgit v1.1