summaryrefslogtreecommitdiffstats
path: root/include/trace
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 /include/trace
parent8efcf34a263965e471e3999904f94d1f6799d42a (diff)
downloadop-kernel-dev-918da95176beb743ff47b3bbfb0a4ee420658a95.zip
op-kernel-dev-918da95176beb743ff47b3bbfb0a4ee420658a95.tar.gz
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 'include/trace')
-rw-r--r--include/trace/events/fsi_master_gpio.h16
1 files changed, 16 insertions, 0 deletions
diff --git a/include/trace/events/fsi_master_gpio.h b/include/trace/events/fsi_master_gpio.h
index f95cf32..33e928c 100644
--- a/include/trace/events/fsi_master_gpio.h
+++ b/include/trace/events/fsi_master_gpio.h
@@ -64,6 +64,22 @@ TRACE_EVENT(fsi_master_gpio_break,
)
);
+
+TRACE_EVENT(fsi_master_gpio_poll_response_busy,
+ TP_PROTO(const struct fsi_master_gpio *master, int busy),
+ TP_ARGS(master, busy),
+ TP_STRUCT__entry(
+ __field(int, master_idx)
+ __field(int, busy)
+ ),
+ TP_fast_assign(
+ __entry->master_idx = master->master.idx;
+ __entry->busy = busy;
+ ),
+ TP_printk("fsi-gpio%d: device reported busy %d times",
+ __entry->master_idx, __entry->busy)
+);
+
#endif /* _TRACE_FSI_MASTER_GPIO_H */
#include <trace/define_trace.h>
OpenPOWER on IntegriCloud