public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: mathieu.poirier@linaro.org
Cc: linux@arm.linux.org.uk, pratikp@codeaurora.org, varshney@ti.com,
	Al.Grant@arm.com, jonas.svennebring@avagotech.com,
	james.king@linaro.org, kaixu.xia@linaro.org,
	marcin.jabrzyk@gmail.com, r.sengupta@samsung.com,
	robbelibobban@gmail.com, patches@linaro.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9 01/12] coresight: add CoreSight core layer framework
Date: Fri, 7 Nov 2014 11:30:16 -0800	[thread overview]
Message-ID: <20141107193016.GA29311@kroah.com> (raw)
In-Reply-To: <1415038066-22423-2-git-send-email-mathieu.poirier@linaro.org>

On Mon, Nov 03, 2014 at 11:07:35AM -0700, mathieu.poirier@linaro.org wrote:
> From: Pratik Patel <pratikp@codeaurora.org>
> 
> CoreSight components are compliant with the ARM CoreSight
> architecture specification and can be connected in various
> topologies to suit a particular SoC tracing needs. These trace
> components can generally be classified as sources, links and
> sinks. Trace data produced by one or more sources flows through
> the intermediate links connecting the source to the currently
> selected sink.
> 
> The CoreSight framework provides an interface for the CoreSight trace
> drivers to register themselves with. It's intended to build up a
> topological view of the CoreSight components and configure the
> correct serie of components on user input via sysfs.
> 
> For eg., when enabling a source, the framework builds up a path
> consisting of all the components connecting the source to the
> currently selected sink(s) and enables all of them.
> 
> The framework also supports switching between available sinks
> and provides status information to user space applications
> through the debugfs interface.
> 
> Signed-off-by: Pratik Patel <pratikp@codeaurora.org>
> Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>

You don't seem to document the sysfs files you create here in
Documentation/ABI/ anywhere in the series.  Can you fix that up?

Other than that minor nit, this looks good to me.  Feel free to take it
through some random ARM tree.

thanks,

greg k-h

  reply	other threads:[~2014-11-07 19:30 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-03 18:07 [PATCH v9 00/12] Coresight framework and drivers mathieu.poirier
2014-11-03 18:07 ` [PATCH v9 01/12] coresight: add CoreSight core layer framework mathieu.poirier
2014-11-07 19:30   ` Greg KH [this message]
2014-11-07 19:30     ` Greg KH
2014-11-07 21:39       ` Mathieu Poirier
2014-11-07 21:48         ` Greg KH
2014-11-03 18:07 ` [PATCH v9 02/12] coresight-tmc: add CoreSight TMC driver mathieu.poirier
2014-11-03 18:07 ` [PATCH v9 03/12] coresight-tpiu: add CoreSight TPIU driver mathieu.poirier
2014-11-03 18:07 ` [PATCH v9 04/12] coresight-etb: add CoreSight ETB driver mathieu.poirier
2014-11-03 18:07 ` [PATCH v9 05/12] coresight-funnel: add CoreSight Funnel driver mathieu.poirier
2014-11-03 18:07 ` [PATCH v9 06/12] coresight-replicator: add CoreSight Replicator driver mathieu.poirier
2014-11-03 18:07 ` [PATCH v9 07/12] coresight-etm: add CoreSight ETM/PTM driver mathieu.poirier
2014-11-10 10:34   ` Paul Bolle
2014-11-10 15:40     ` Mathieu Poirier
2014-11-10 19:32       ` Paul Bolle
2015-01-12 11:34         ` Paul Bolle
2015-01-12 15:05           ` Mathieu Poirier
2014-11-03 18:07 ` [PATCH v9 08/12] coresight: documentation for coresight framework and drivers mathieu.poirier
2014-11-03 18:07 ` [PATCH v9 09/12] coresight: adding support for beagle and beagleXM mathieu.poirier
2014-11-03 18:07 ` [PATCH v9 10/12] coresight: adding basic support for Vexpress TC2 mathieu.poirier
2014-11-03 18:07 ` [PATCH v9 11/12] coresight: adding basic support for D01 board mathieu.poirier
2014-11-03 18:07 ` [PATCH v9 12/12] ARM: removing support for etb/etm in "arch/arm/kernel/" mathieu.poirier

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=20141107193016.GA29311@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Al.Grant@arm.com \
    --cc=james.king@linaro.org \
    --cc=jonas.svennebring@avagotech.com \
    --cc=kaixu.xia@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=marcin.jabrzyk@gmail.com \
    --cc=mathieu.poirier@linaro.org \
    --cc=patches@linaro.org \
    --cc=pratikp@codeaurora.org \
    --cc=r.sengupta@samsung.com \
    --cc=robbelibobban@gmail.com \
    --cc=varshney@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox