From 495787a792ac498843b25e5569597c24cd026f2b Mon Sep 17 00:00:00 2001 From: Alex Elder Date: Fri, 3 Jun 2016 15:55:38 -0500 Subject: greybus: tracing: add timing traces Bryan reports he used certain message traces to determine when time sync messages transit the boundary between the Greybus core and the host device. This patch adds two trace events--one a message event for outbound messages (because it indicates its operation and its destination), and one host device event for incoming messages (because message information isn't available as early as desired). These events are being created to allow the same sort of analysis of messages without having to store extra information for every message trace. (The next patch changes the information a message trace records.) Signed-off-by: Alex Elder Reviewed-by: Viresh Kumar Signed-off-by: Greg Kroah-Hartman --- drivers/staging/greybus/hd.c | 3 +++ 1 file changed, 3 insertions(+) (limited to 'drivers/staging/greybus/hd.c') diff --git a/drivers/staging/greybus/hd.c b/drivers/staging/greybus/hd.c index 12ac0b6..6d952ba 100644 --- a/drivers/staging/greybus/hd.c +++ b/drivers/staging/greybus/hd.c @@ -13,6 +13,9 @@ #include "greybus.h" #include "greybus_trace.h" +EXPORT_TRACEPOINT_SYMBOL_GPL(gb_message_submit); +EXPORT_TRACEPOINT_SYMBOL_GPL(gb_hd_in); + static struct ida gb_hd_bus_id_map; int gb_hd_output(struct gb_host_device *hd, void *req, u16 size, u8 cmd, -- cgit v1.1