From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] coresight: bindings for debug module
Date: Fri, 3 Mar 2017 00:21:24 -0600 [thread overview]
Message-ID: <20170303062124.rc2fw6axs3cp7ofc@rob-hp-laptop> (raw)
In-Reply-To: <1488294420-14188-2-git-send-email-leo.yan@linaro.org>
On Tue, Feb 28, 2017 at 11:06:58PM +0800, Leo Yan wrote:
> According to ARMv8 architecture reference manual (ARM DDI 0487A.k)
> Chapter 'Part H: External debug', the CPU can integrate debug module
> and it can support self-hosted debug and external debug. Especially
> for supporting self-hosted debug, this means the program can access
> the debug module from mmio region; and usually the mmio region is
> integrated with coresight.
>
> So add document for binding debug component, includes binding to APB
> clock; and also need specify the CPU node which the debug module is
> dedicated to specific CPU.
>
> Suggested-by: Mike Leach <mike.leach@linaro.org>
> Signed-off-by: Leo Yan <leo.yan@linaro.org>
> ---
> .../devicetree/bindings/arm/coresight-debug.txt | 40 ++++++++++++++++++++++
> 1 file changed, 40 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/arm/coresight-debug.txt
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2017-03-03 6:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 15:06 [PATCH v2 0/3] coresight: enable debug module Leo Yan
2017-02-28 15:06 ` [PATCH v2 1/3] coresight: bindings for " Leo Yan
2017-03-01 15:45 ` Mathieu Poirier
2017-03-02 0:43 ` Leo Yan
2017-03-03 6:21 ` Rob Herring [this message]
2017-02-28 15:06 ` [PATCH v2 2/3] coresight: refactor with function of_coresight_get_cpu Leo Yan
2017-03-01 16:02 ` Mathieu Poirier
2017-03-02 0:39 ` Leo Yan
2017-02-28 15:07 ` [PATCH v2 3/3] coresight: add support for debug module Leo Yan
2017-03-01 17:35 ` Mathieu Poirier
2017-03-02 0:37 ` Leo Yan
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=20170303062124.rc2fw6axs3cp7ofc@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