Received: by 10.223.176.5 with SMTP id f5csp2664051wra; Mon, 5 Feb 2018 07:52:01 -0800 (PST) X-Google-Smtp-Source: AH8x224Y4wjP+RCUTaWfyPaPuysP2TD/90cJ5jAO0xIgGy/bdoz4zgoIYrtoWJateDwIPZw9JY1T X-Received: by 10.99.173.5 with SMTP id g5mr38709986pgf.391.1517845921183; Mon, 05 Feb 2018 07:52:01 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517845921; cv=none; d=google.com; s=arc-20160816; b=JZ9X1I2LjAV7Fs6VMo+Z4ygK80tJtfb5mrh2GDam88bN2XuiexlCSeCGSlRJkNlfFx piVTufbkJSElX7UJyRk5akfJhiWcN64dtMIC2pLRmv8rRXDwSm+546m5sF6qM+P+P3MS xlMxWa0/Lh5FiZo53RwEL6Y35STS+42MjGXR4CXgpLJMUpuYyz6CKiJVegztJ2OJH2YT XdnoHit0rJH1+oduskJhSDuhJGYszZPTpioE8P8Sxh7SVJaxthcohfLc33+5fKnunhdX Vda2ivme0/GgEeeHFBUeSL23gxmYDgNwQ+IgCqZ6KvqRF4P9LSnJC1WTmLyKkTM1NlQt SoYQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dmarc-filter:dkim-signature:dkim-signature :arc-authentication-results; bh=D/QHU0OdYoyjKgfyOF/rA77N8fsL0n5qxZd3t21O8Zc=; b=pmPIqOVKwDuVr2e6uqQe//zBdBzOjP1zQUxxn7pxP/RW8cZ0KCSVCeKQ8Y+XeuA3Wj 6JpZA/cvvcRPi7fIzOXydo0fvVnxNwrfQnQ2Bx2yrnXTGeTtERQ2geBO9NPEGbtbsilh GKt4kvt4GkRGaPTYdilACIMIjJjU/zS42yzahLvoAXkj4IEOFpETIiMD9+JhDDMdIADl QXav1r070nWBqwyD4VctVJ9Xk+NWPS9JpemRMJPrQZzRgKqLc6Bd+EKdm8X8vm6zYMho qQpCzX8JUFnnfXrjgwYJOJia7ncoN6kR9yMrK65ZsBox500p0s/eIIdgYUm0/WRASz0w HYeA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=IE1/FTAD; dkim=pass header.i=@codeaurora.org header.s=default header.b=UDccTpqi; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t15si4898620pfh.101.2018.02.05.07.51.41; Mon, 05 Feb 2018 07:52:01 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=IE1/FTAD; dkim=pass header.i=@codeaurora.org header.s=default header.b=UDccTpqi; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753215AbeBEPu4 (ORCPT + 99 others); Mon, 5 Feb 2018 10:50:56 -0500 Received: from smtp.codeaurora.org ([198.145.29.96]:58584 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752767AbeBEPuv (ORCPT ); Mon, 5 Feb 2018 10:50:51 -0500 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id DFA8E60A00; Mon, 5 Feb 2018 15:50:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1517845850; bh=PMnur3lvEpG/TzPN0a9bRDPNn6O/UuFx2My4Ig1xfoU=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=IE1/FTADo/WMASpo+xmGdOUB0YY05XNc/Bs6pzUhmpAOXJCCCuDdK4bJyE0NICrqh 4RueGfrHGxfgQWfjF4DETMNdS2YmOaZPrdJhbPUGG46eTqQ4sxKyotIM8Tmd7TjzpP LxIF1C8dXJtZXWg2ptVinzddnaXUsHhyhxZWPdE0= X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on pdx-caf-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.8 required=2.0 tests=ALL_TRUSTED,BAYES_00, DKIM_SIGNED,T_DKIM_INVALID autolearn=no autolearn_force=no version=3.4.0 Received: from localhost (i-global254.qualcomm.com [199.106.103.254]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: ilina@smtp.codeaurora.org) by smtp.codeaurora.org (Postfix) with ESMTPSA id E4EBC6022B; Mon, 5 Feb 2018 15:50:48 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1517845849; bh=PMnur3lvEpG/TzPN0a9bRDPNn6O/UuFx2My4Ig1xfoU=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=UDccTpqiZAmFK5IqY/CyK8dMFfSJPAbYta5QWDtY7ydLpaVIj0zc6YWBm9t+D4Mmf Nsj10OFMT/kQk0WFU9WodB0H49fsdGhP3EGQbYCWgE5Va5cT9ThRgkWFQhn7P0AQco wRheVQlJyfb1NG0RV6EOP8LKYfUG7/BEiueDReY4= DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org E4EBC6022B Authentication-Results: pdx-caf-mail.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: pdx-caf-mail.web.codeaurora.org; spf=none smtp.mailfrom=ilina@codeaurora.org Date: Mon, 5 Feb 2018 15:50:48 +0000 From: Lina Iyer To: tglx@linutronix.de, jason@lakedaemon.net, marc.zyngier@arm.com Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, sboyd@codeaurora.org, rnayak@codeaurora.org, asathyak@codeaurora.org, Steven Rostedt Subject: Re: [PATCH RFC v2 3/3] drivers: irqchip: pdc: log PDC info in FTRACE Message-ID: <20180205155048.GA22036@codeaurora.org> References: <20180202142200.6229-1-ilina@codeaurora.org> <20180202142200.6229-4-ilina@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20180202142200.6229-4-ilina@codeaurora.org> User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Steve, On Fri, Feb 02 2018 at 14:22 +0000, Lina Iyer wrote: >From: Archana Sathyakumar > >Log key PDC pin configuration in FTRACE. > >Cc: Steven Rostedt >Signed-off-by: Archana Sathyakumar >Signed-off-by: Lina Iyer >--- > 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 > #include > #include >+#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