[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKohponm0CbBNLY19B-9ccfe3d3jreSJLDePEROR+w1=1JZEWw@mail.gmail.com>
Date: Wed, 25 Jul 2018 09:20:45 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Joel Fernandes <joel@...lfernandes.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"Cc: Android Kernel" <kernel-team@...roid.com>,
Ruchi Kandoi <kandoiruchi@...gle.com>,
Ingo Molnar <mingo@...hat.com>,
Jonathan Corbet <corbet@....net>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [PATCH v3] cpufreq: trace frequency limits change
On 24 July 2018 at 23:05, Joel Fernandes <joel@...lfernandes.org> wrote:
> From: Ruchi Kandoi <kandoiruchi@...gle.com>
>
> systrace used for tracing for Android systems has carried a patch for
> many years in the Android tree that traces when the cpufreq limits
> change. With the help of this information, systrace can know when the
> policy limits change and can visually display the data. Lets add
> upstream support for the same.
>
> Signed-off-by: Ruchi Kandoi <kandoiruchi@...gle.com>
> Signed-off-by: Joel Fernandes (Google) <joel@...lfernandes.org>
> ---
> Viresh since I changed the patch, could you Ack it again?
>
> v2->v3: reduce parameters to tracepoint call (Steve)
> v1->v2: correct ordering of min/max (Viresh)
>
> Documentation/trace/events-power.rst | 1 +
> drivers/cpufreq/cpufreq.c | 1 +
> include/trace/events/power.h | 25 +++++++++++++++++++++++++
> 3 files changed, 27 insertions(+)
Acked-by: Viresh Kumar <viresh.kumar@...aro.org>
Powered by blists - more mailing lists