From: Darren Hart <dvhart@infradead.org>
To: Souvik Kumar Chakravarty <souvik.k.chakravarty@intel.com>
Cc: platform-driver-x86@vger.kernel.org, rjw@rjwysocki.net,
linux-kernel@vger.kernel.org, srinidhi.kasagar@intel.com,
qipeng.zha@intel.com, rajeev.d.muralidhar@intel.com,
sukumar.ghorai@intel.com, ong.hock.yu@intel.com,
aubrey.li@intel.com, david.ginat@intel.com
Subject: Re: [PATCH v2 0/4] Add Intel Telemetry Support
Date: Thu, 14 Jan 2016 14:38:59 -0800 [thread overview]
Message-ID: <20160114223859.GD1989@malice.jf.intel.com> (raw)
In-Reply-To: <1452594613-20409-1-git-send-email-souvik.k.chakravarty@intel.com>
On Tue, Jan 12, 2016 at 04:00:13PM +0530, Souvik Kumar Chakravarty wrote:
> This set of 4 patches enables PM Telemetry Support for Intel
> Platforms. Intel PM Telemetry is a software mechanism via which
> various SoC PM and performance related parameters like PM counters,
> firmware trace verbosity, the status of different devices inside
> the SoC, etc can be monitored and analyzed.
> The statictics are fetched via IPC from the Punit & PMC firmware
> and hence it depends on the PMC & PUNIT IPC driver. The different
> samples that may be monitored can be configured at runtime via
> exported APIs.
>
> Currently it supports Intel ApolloLake platform and is intended to
> be extended to future platforms as well.
Thank you for sticking with this and seeing it through Souvik, this was an
unusually long merge process with the dependency on the punit driver and the
changes in underwent.
I have queued this to testing. Pending any issues from the CI robots, it'll hit
next by tomorrow, and still make this merge window.
--
Darren Hart
Intel Open Source Technology Center
next prev parent reply other threads:[~2016-01-14 22:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 10:30 [PATCH v2 0/4] Add Intel Telemetry Support Souvik Kumar Chakravarty
2016-01-14 22:38 ` Darren Hart [this message]
2016-01-18 3:01 ` Chakravarty, Souvik K
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=20160114223859.GD1989@malice.jf.intel.com \
--to=dvhart@infradead.org \
--cc=aubrey.li@intel.com \
--cc=david.ginat@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ong.hock.yu@intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=qipeng.zha@intel.com \
--cc=rajeev.d.muralidhar@intel.com \
--cc=rjw@rjwysocki.net \
--cc=souvik.k.chakravarty@intel.com \
--cc=srinidhi.kasagar@intel.com \
--cc=sukumar.ghorai@intel.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.