From: Darren Hart <dvhart@infradead.org>
To: Souvik Kumar Chakravarty <souvik.k.chakravarty@intel.com>,
Rafael Wysocki <rjw@rjwysocki.net>
Cc: platform-driver-x86@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
Subject: Re: [PATCH v3 5/5] platform:x86: Makefile/Kconfig/MAINTAINERS changes for Intel Telemetry
Date: Tue, 29 Dec 2015 16:59:10 -0800 [thread overview]
Message-ID: <20151230005910.GD29978@malice.jf.intel.com> (raw)
In-Reply-To: <1450867481-11404-1-git-send-email-souvik.k.chakravarty@intel.com>
On Wed, Dec 23, 2015 at 04:14:41PM +0530, Souvik Kumar Chakravarty wrote:
> Makefile, Kconfig & MAINTAINERS changes for compiling Telemetry.
> It depends on PUNIT and PMC IPC drivers.
...
> +config INTEL_TELEMETRY
> + tristate "Intel SoC Telemetry Driver"
> + default n
> + depends on INTEL_PMC_IPC && INTEL_PUNIT_IPC && X86_64
> + ---help---
> + This driver provides interfaces to configure and use
> + telemetry for INTEL SoC from APL onwards. It is also
> + used to get various SoC events and parameters
> + directly via debugfs files. Various tools may use
If tools are going to be relying on it, debugfs doesn't seem like the right
place for it to me. Would /sys/power be more apt?
Rafael?
--
Darren Hart
Intel Open Source Technology Center
next prev parent reply other threads:[~2015-12-30 0:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 10:44 [PATCH v3 5/5] platform:x86: Makefile/Kconfig/MAINTAINERS changes for Intel Telemetry Souvik Kumar Chakravarty
2015-12-30 0:59 ` Darren Hart [this message]
2015-12-30 1:59 ` Rafael J. Wysocki
2015-12-30 7:32 ` Darren Hart
-- strict thread matches above, loose matches on Subject: below --
2016-01-07 9:08 Souvik Kumar Chakravarty
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=20151230005910.GD29978@malice.jf.intel.com \
--to=dvhart@infradead.org \
--cc=aubrey.li@intel.com \
--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.