Hi Steve, On Fri, Feb 02 2018 at 14:22 +0000, Lina Iyer wrote:
From: Archana Sathyakumar <asathyak@xxxxxxxxxxxxxx> Log key PDC pin configuration in FTRACE. Cc: Steven Rostedt <rostedt@xxxxxxxxxxx> Signed-off-by: Archana Sathyakumar <asathyak@xxxxxxxxxxxxxx> Signed-off-by: Lina Iyer <ilina@xxxxxxxxxxxxxx> --- drivers/irqchip/qcom-pdc.c | 7 ++++++ include/trace/events/pdc.h | 55 ++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 62 insertions(+) create mode 100644 include/trace/events/pdc.h diff --git a/drivers/irqchip/qcom-pdc.c b/drivers/irqchip/qcom-pdc.c index a392380eada6..7f177ad88713 100644 --- a/drivers/irqchip/qcom-pdc.c +++ b/drivers/irqchip/qcom-pdc.c @@ -26,6 +26,8 @@ #include <linux/platform_device.h> #include <linux/slab.h> #include <linux/types.h> +#define CREATE_TRACE_POINTS +#include "trace/events/pdc.h"
In addition to this PDC patch, there are a few drivers with FTRACE support coming for up QCOM SoCs. Would it make sense to open up a new sub-folder for SoC specific FTRACE like say, trace/events/soc/ trace/events/soc/qcom/ What would be your recommendation? At the very least, I am thinking of renaming this file to trace/events/qcom-pdc.h. Thanks, Lina -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
