summaryrefslogtreecommitdiffstats
path: root/drivers/fsi
diff options
context:
space:
mode:
authorAndrew Jeffery <andrew@aj.id.au>2018-02-20 14:48:33 +1030
committerBenjamin Herrenschmidt <benh@kernel.crashing.org>2018-06-12 14:04:13 +1000
commit918da95176beb743ff47b3bbfb0a4ee420658a95 (patch)
tree6b60ae01368fc4b4c3ddc9dab0679496aae4d61c /drivers/fsi
parent8efcf34a263965e471e3999904f94d1f6799d42a (diff)
downloadlinux-918da95176beb743ff47b3bbfb0a4ee420658a95.tar.bz2
fsi: gpio: Trace busy count
An observation from trace output of the existing FSI tracepoints was that the remote device was sometimes reporting as busy. Add a new tracepoint reporting the busy count in order to get a better grip on how often this is the case. Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Acked-by: Eddie James <eajames@linux.vnet.ibm.com> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org> Tested-by: Joel Stanley <joel@jms.id.au>
Diffstat (limited to 'drivers/fsi')
-rw-r--r--drivers/fsi/fsi-master-gpio.c3
1 files changed, 3 insertions, 0 deletions
diff --git a/drivers/fsi/fsi-master-gpio.c b/drivers/fsi/fsi-master-gpio.c
index 3f487449a277..2a49b167effe 100644
--- a/drivers/fsi/fsi-master-gpio.c
+++ b/drivers/fsi/fsi-master-gpio.c
@@ -401,6 +401,9 @@ retry:
break;
}
+ if (busy_count > 0)
+ trace_fsi_master_gpio_poll_response_busy(master, busy_count);
+
/* Clock the slave enough to be ready for next operation */
clock_zeros(master, FSI_GPIO_PRIME_SLAVE_CLOCKS);
return rc;