be1a71a128
In order to have an easier way to debug issues, create trace events (using the ftrace framework) that will allow us to follow exactly what the driver is doing with the device. The text format isn't all that useful, but the binary format can also be obtained easily via debugfs and then analysed on the fly or offline with debugging tools. Signed-off-by: Johannes Berg <johannes@sipsolutions.net> Signed-off-by: Reinette Chatre <reinette.chatre@intel.com> Signed-off-by: John W. Linville <linville@tuxdriver.com>
13 lines
394 B
C
13 lines
394 B
C
#include <linux/module.h>
|
|
|
|
/* sparse doesn't like tracepoint macros */
|
|
#ifndef __CHECKER__
|
|
#define CREATE_TRACE_POINTS
|
|
#include "iwl-devtrace.h"
|
|
|
|
EXPORT_TRACEPOINT_SYMBOL(iwlwifi_dev_ioread32);
|
|
EXPORT_TRACEPOINT_SYMBOL(iwlwifi_dev_iowrite32);
|
|
EXPORT_TRACEPOINT_SYMBOL(iwlwifi_dev_rx);
|
|
EXPORT_TRACEPOINT_SYMBOL(iwlwifi_dev_ucode_event);
|
|
EXPORT_TRACEPOINT_SYMBOL(iwlwifi_dev_ucode_error);
|
|
#endif
|