[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20210312180841.GA29093@amd>
Date: Fri, 12 Mar 2021 19:08:42 +0100
From: Pavel Machek <pavel@....cz>
To: Peiyong Lin <lpy@...gle.com>
Cc: Brian Starkey <brian.starkey@....com>, alexdeucher@...il.com,
android-kernel@...gle.com, dri-devel@...ts.freedesktop.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...hat.com>,
nd@....com, Paul Walmsley <paul.walmsley@...ive.com>,
Prahlad Kilambi <prahladk@...gle.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
Steven Rostedt <rostedt@...dmis.org>,
Sidath Senanayake <sidaths@...gle.com>,
Ulf Hansson <ulf.hansson@...aro.org>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
zzyiwei@...roid.com
Subject: Re: [PATCH v5] Add power/gpu_frequency tracepoint.
On Wed 2021-03-10 13:56:29, Peiyong Lin wrote:
> On Mon, Dec 21, 2020 at 12:10 PM 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.
...
> > /* This part must be outside protection */
> > --
> > 2.29.2.684.gfbc64c5ab5-goog
> >
>
> Hi there,
>
> Could you please take a look at this patch?
Please trim email quotes when replying.
Also, you might want to state _name_ of person who should apply this,
so there's no ambiguity. You cc-ed many people...
Pavel
--
http://www.livejournal.com/~pavelmachek
Download attachment "signature.asc" of type "application/pgp-signature" (182 bytes)
Powered by blists - more mailing lists