From: tixy@linaro.org (Jon Medhurst (Tixy))
To: linux-arm-kernel@lists.infradead.org
Subject: [Patch v3 2/3] ARM: dts: Document the CCI PMU DT bindings
Date: Fri, 30 Aug 2013 14:59:40 +0100 [thread overview]
Message-ID: <1377871180.3655.41.camel@linaro1.home> (raw)
In-Reply-To: <1377183748-5717-3-git-send-email-punit.agrawal@arm.com>
On Thu, 2013-08-22 at 16:02 +0100, Punit Agrawal wrote:
> The CCI PMU can profile bus transactions at the master and slave
> interfaces of the CCI. The PMU can be used to observe an aggregated
> view of the bus traffic between the various components connected to the
> CCI.
>
> Introduce a binding for the CCI PMU. The PMU node will be a sub-node of
> the CCI node.
>
> Cc: devicetree at vger.kernel.org
> Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> Cc: Nicolas Pitre <nicolas.pitre@linaro.org>
> Cc: Stephen Warren <swarren@wwwdotorg.org>
> Cc: Kumar Gala <galak@codeaurora.org>
> Cc: Rob Herring <rob.herring@calxeda.com>
> Signed-off-by: Punit Agrawal <punit.agrawal@arm.com>
> ---
> Documentation/devicetree/bindings/arm/cci.txt | 46 +++++++++++++++++++++++++
> 1 file changed, 46 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/cci.txt b/Documentation/devicetree/bindings/arm/cci.txt
> index 024c03d..551119e 100644
> --- a/Documentation/devicetree/bindings/arm/cci.txt
> +++ b/Documentation/devicetree/bindings/arm/cci.txt
> @@ -85,6 +85,42 @@ specific to ARM.
> corresponding interface programming
> registers.
>
> + - CCI PMU node
> +
> + Parent node must be CCI interconnect node.
> +
> + A CCI pmu node must contain the following properties:
> +
> + - compatible
> + Usage: required
> + Value type: <string>
> + Definition: must be "arm,cci-400-pmu"
> +
> + - reg:
> + Usage: required
> + Value type: Integer cells. A register entry, expressed
> + as a pair of cells, containing base and
> + size.
> + Definition: the base address and size of the
> + corresponding interface programming
> + registers.
> +
> + - interrupts:
> + Usage: required
> + Value type: Integer cells. Array of interrupt specifier
> + entries, as defined in
> + ../interrupt-controller/interrupts.txt.
> + Definition: list of counter overflow interrupts, one per
> + counter. The interrupts must be specified
> + starting with the cycle counter overflow
> + interrupt, followed by counter0 overflow
> + interrupt, counter1 overflow interrupt,...
> + ,counterN overflow interrupt.
> +
> + The CCI PMU has an interrupt signal for each
> + counter. The number of interrupts must be
> + equal to the number of counters.
> +
> * CCI interconnect bus masters
>
> Description: masters in the device tree connected to a CCI port
> @@ -169,6 +205,16 @@ Example:
> interface-type = "ace";
> reg = <0x5000 0x1000>;
> };
> +
> + pmu at 9000 {
> + compatible = "arm,cci-400-pmu";
> + reg = <0x9000 0x5000>;
> + interrupts = <0 101 4>,
> + <0 102 4>,
> + <0 103 4>,
> + <0 104 4>,
> + <0 105 4>;
> + };
> };
>
> This CCI node corresponds to a CCI component whose control registers sits
It's not shown in the diff above, but the documentation gives the
following for the cci node:
ranges = <0x0 0x0 0x2c090000 0x6000>;
which doesn't include the PMU nodes, so should that 0x6000 also be
changed to 0x10000 (the full range of addresses in the TRM).
--
Tixy
next prev parent reply other threads:[~2013-08-30 13:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 15:02 [Patch v3 0/3] Add CCI PMU support Punit Agrawal
2013-08-22 15:02 ` [Patch v3 1/3] ARM: dts: Improve CCI bindings documentation Punit Agrawal
2013-08-22 22:15 ` Stephen Warren
2013-08-22 15:02 ` [Patch v3 2/3] ARM: dts: Document the CCI PMU DT bindings Punit Agrawal
2013-08-22 22:17 ` Stephen Warren
2013-08-23 9:56 ` Punit Agrawal
2013-08-30 13:59 ` Jon Medhurst (Tixy) [this message]
2013-08-30 14:36 ` Punit Agrawal
2013-08-30 16:17 ` Kumar Gala
2013-09-04 12:26 ` Punit Agrawal
2013-09-05 12:51 ` Will Deacon
2013-08-22 15:02 ` [Patch v3 3/3] drivers: CCI: add ARM CCI PMU support Punit Agrawal
2013-08-30 11:24 ` Will Deacon
2013-08-30 14:34 ` Punit Agrawal
2013-08-30 14:37 ` Will Deacon
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=1377871180.3655.41.camel@linaro1.home \
--to=tixy@linaro.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).