All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Peiyong Lin <lpy@google.com>
Cc: Sidath Senanayake <sidaths@google.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	Prahlad Kilambi <prahladk@google.com>,
	Ingo Molnar <mingo@redhat.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	nd@arm.com, zzyiwei@android.com, android-kernel@google.com
Subject: Re: [PATCH v5] Add power/gpu_frequency tracepoint.
Date: Fri, 12 Mar 2021 19:08:42 +0100	[thread overview]
Message-ID: <20210312180841.GA29093@amd> (raw)
In-Reply-To: <CA+0soAnXOknfWBbuHiq4VG8byoQ89u8NdYBtq-n-JMURPUOhUw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1062 bytes --]

On Wed 2021-03-10 13:56:29, Peiyong Lin wrote:
> On Mon, Dec 21, 2020 at 12:10 PM Peiyong Lin <lpy@google.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

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@ucw.cz>
To: Peiyong Lin <lpy@google.com>
Cc: Brian Starkey <brian.starkey@arm.com>,
	alexdeucher@gmail.com, android-kernel@google.com,
	dri-devel@lists.freedesktop.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
	nd@arm.com, Paul Walmsley <paul.walmsley@sifive.com>,
	Prahlad Kilambi <prahladk@google.com>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Sidath Senanayake <sidaths@google.com>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	zzyiwei@android.com
Subject: Re: [PATCH v5] Add power/gpu_frequency tracepoint.
Date: Fri, 12 Mar 2021 19:08:42 +0100	[thread overview]
Message-ID: <20210312180841.GA29093@amd> (raw)
In-Reply-To: <CA+0soAnXOknfWBbuHiq4VG8byoQ89u8NdYBtq-n-JMURPUOhUw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]

On Wed 2021-03-10 13:56:29, Peiyong Lin wrote:
> On Mon, Dec 21, 2020 at 12:10 PM Peiyong Lin <lpy@google.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

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2021-03-12 18:08 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-13 21:03 [PATCH] Add power/gpu_frequency tracepoint Peiyong Lin
2020-08-13 21:22 ` Steven Rostedt
2020-08-13 21:37   ` [PATCH v2] " Peiyong Lin
2020-08-13 21:50     ` Steven Rostedt
2020-08-20 19:41       ` [PATCH v3] " Peiyong Lin
2020-08-20 20:27         ` Steven Rostedt
2020-10-22 16:59           ` [PATCH] " Peiyong Lin
2020-10-22 17:34           ` [PATCH v4] " Peiyong Lin
2020-10-26 22:25             ` Peiyong Lin
2020-10-27  6:16               ` Greg Kroah-Hartman
2020-11-16 20:55             ` Peiyong Lin
2020-11-16 21:05               ` Steven Rostedt
2020-11-17 18:00                 ` Rafael J. Wysocki
2020-11-17 18:00                   ` Rafael J. Wysocki
2020-11-17 18:10                   ` Alex Deucher
2020-11-17 18:10                     ` Alex Deucher
2020-11-17 21:31             ` Peiyong Lin
2020-11-17 21:31               ` Peiyong Lin
2020-11-30 22:33               ` Peiyong Lin
2020-11-30 22:33                 ` Peiyong Lin
2020-12-02 12:34                 ` Brian Starkey
2020-12-02 12:34                   ` Brian Starkey
2020-12-21 20:10                   ` [PATCH v5] " Peiyong Lin
2020-12-21 20:10                     ` Peiyong Lin
2021-03-10 21:56                     ` Peiyong Lin
2021-03-10 21:56                       ` Peiyong Lin
2021-03-12 18:08                       ` Pavel Machek [this message]
2021-03-12 18:08                         ` Pavel Machek
     [not found] ` <159741850487.10342.14268227307882225260@build.alporthouse.com>
2020-08-14 19:25   ` [PATCH] " Peiyong Lin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210312180841.GA29093@amd \
    --to=pavel@ucw.cz \
    --cc=android-kernel@google.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lpy@google.com \
    --cc=mingo@redhat.com \
    --cc=nd@arm.com \
    --cc=paul.walmsley@sifive.com \
    --cc=prahladk@google.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rostedt@goodmis.org \
    --cc=sidaths@google.com \
    --cc=ulf.hansson@linaro.org \
    --cc=yamada.masahiro@socionext.com \
    --cc=zzyiwei@android.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.