From: Bryan O'Donoghue Date: Tue, 2 Aug 2016 12:18:29 +0000 (+0100) Subject: greybus: timesync: Printout strobe count on sync failure X-Git-Tag: v4.9-rc1~119^2~378^2~21^2~86 X-Git-Url: https://git.karo-electronics.de/?a=commitdiff_plain;h=ca9551f6815efd4e7bbdee0cd2c71c368ebdf92c;p=karo-tx-linux.git greybus: timesync: Printout strobe count on sync failure If we failed to synchronize the FrameTime it would be useful to know how many of the expected strobes arrived, for example a value of 0/5 would indicate the SVC was completely dead but a value of 4/5 would indicate one GPIO pulse got lost i.e. the AP was too slow reacting to an interrupt and completely missed one of the strobe events. In either case the actual number of strobes is a useful thing to print out. Signed-off-by: Bryan O'Donoghue Reviewed-by: Alex Elder Reviewed-by: Vaibhav Hiremath Signed-off-by: Greg Kroah-Hartman --- diff --git a/drivers/staging/greybus/timesync.c b/drivers/staging/greybus/timesync.c index 561bbea9ae17..2e68af7dea6d 100644 --- a/drivers/staging/greybus/timesync.c +++ b/drivers/staging/greybus/timesync.c @@ -772,7 +772,8 @@ static void gb_timesync_worker(struct work_struct *work) case GB_TIMESYNC_STATE_WAIT_SVC: dev_err(×ync_svc->svc->dev, - "timeout SVC strobe completion\n"); + "timeout SVC strobe completion %d/%d\n", + timesync_svc->strobe, GB_TIMESYNC_MAX_STROBES); gb_timesync_teardown(timesync_svc); break;