[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200813175037.48a16064@oasis.local.home>
Date: Thu, 13 Aug 2020 17:50:37 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Peiyong Lin <lpy@...gle.com>
Cc: amit.kucheria@...aro.org, android-kernel@...gle.com,
gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
mingo@...hat.com, paul.walmsley@...ive.com, pavel@....cz,
prahladk@...gle.com, rafael.j.wysocki@...el.com,
ulf.hansson@...aro.org, yamada.masahiro@...ionext.com
Subject: Re: [PATCH v2] Add power/gpu_frequency tracepoint.
On Thu, 13 Aug 2020 14:37:03 -0700
Peiyong Lin <lpy@...gle.com> wrote:
> Historically there is no common trace event for GPU frequency, in
> downstream Android each different hardware vendor implements their own
> way to expose GPU frequency, for example as a debugfs node. This patch
> standardize it as a common trace event in upstream linux kernel to help
> the ecosystem have a common implementation across hardware vendors.
> Toolings in the Linux ecosystem will benefit from this especially in the
> downstream Android, where this information is critical to graphics
> developers.
>
> Signed-off-by: Peiyong Lin <lpy@...gle.com>
> ---
>
> Changelog since v1:
> - Use %u in TP_printk
>
For just the tracing side of this, but the use case is up for others to do:
Reviewed-by: Steven Rostedt (VMware) <rostedt@...dmis.org>
-- Steve
Powered by blists - more mailing lists