From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 4/6] dts: bindings: Document device tree binding for CATU
Date: Mon, 25 Jun 2018 14:46:12 -0600 [thread overview]
Message-ID: <20180625204612.GA15054@rob-hp-laptop> (raw)
In-Reply-To: <20180625112213.23492-5-suzuki.poulose@arm.com>
On Mon, Jun 25, 2018 at 12:22:11PM +0100, Suzuki K Poulose wrote:
> Document CATU device-tree bindings. CATU augments the TMC-ETR
> by providing an improved Scatter Gather mechanism for streaming
> trace data to non-contiguous system RAM pages.
>
> Cc: devicetree at vger.kernel.org
> Cc: frowand.list at gmail.com
> Cc: Rob Herring <robh@kernel.org>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
> Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>
> ---
> .../devicetree/bindings/arm/coresight.txt | 53 ++++++++++++++++++++++
> 1 file changed, 53 insertions(+)
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2018-06-25 20:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 11:22 [PATCH v2 0/6] coresight: Coresight Address Translation Unit support Suzuki K Poulose
2018-06-25 11:22 ` [PATCH v2 1/6] coresight: Cleanup device subtype struct Suzuki K Poulose
2018-06-25 11:22 ` [PATCH v2 2/6] coresight: Add helper device type Suzuki K Poulose
2018-06-25 11:22 ` [PATCH v2 3/6] coresight: Introduce support for Coresight Address Translation Unit Suzuki K Poulose
2018-06-25 16:23 ` Joe Perches
2018-06-26 15:59 ` Mathieu Poirier
2018-06-26 17:19 ` Joe Perches
2018-06-25 11:22 ` [PATCH v2 4/6] dts: bindings: Document device tree binding for CATU Suzuki K Poulose
2018-06-25 20:46 ` Rob Herring [this message]
2018-06-25 11:22 ` [PATCH v2 5/6] coresight: catu: Add support for scatter gather tables Suzuki K Poulose
2018-06-25 11:22 ` [PATCH v2 6/6] coresight: catu: Plug in CATU as a backend for ETR buffer Suzuki K Poulose
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=20180625204612.GA15054@rob-hp-laptop \
--to=robh@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).