From: Robin Murphy <robin.murphy@arm.com>
To: Rob Herring <robh@kernel.org>
Cc: Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
devicetree@vger.kernel.org, "Saidi, Ali" <alisaidi@amazon.com>,
tsahee@amazon.com, harb@amperecomputing.com,
tuanphan@os.amperecomputing.com, james.yang@arm.com,
patrik.berglund@arm.com
Subject: Re: [PATCH v2.1 1/3] perf: Add Arm CMN-600 DT binding
Date: Sat, 19 Sep 2020 01:23:45 +0100 [thread overview]
Message-ID: <152e2d42-9ace-f78b-145a-5882ce936c3e@arm.com> (raw)
In-Reply-To: <CAL_JsqKQUyp4tUrw149yF5PHgz6HQ3_Szy1PD=L8=pzU_vWotw@mail.gmail.com>
On 2020-09-18 19:54, Rob Herring wrote:
> On Fri, Sep 18, 2020 at 12:24 PM Robin Murphy <robin.murphy@arm.com> wrote:
>>
>> Document the requirements for the CMN-600 DT binding. The internal
>> topology is almost entirely discoverable by walking a tree of ID
>> registers, but sadly both the starting point for that walk and the
>> exact format of those registers are configuration-dependent and not
>> discoverable from some sane fixed location. Oh well.
>>
>> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
>> ---
>>
>> fix up $id as well, oops...
>>
>> .../devicetree/bindings/perf/arm,cmn.yaml | 57 +++++++++++++++++++
>> 1 file changed, 57 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/perf/arm,cmn.yaml
>
> Do you expect this to cover more than cmn-600? If not, use the
> compatible string for the file name.
As far as I'm aware, future CMN products will maintain the same general
PMU design, but with enough subtle differences to deserve their own
compatible strings.
>> diff --git a/Documentation/devicetree/bindings/perf/arm,cmn.yaml b/Documentation/devicetree/bindings/perf/arm,cmn.yaml
>> new file mode 100644
>> index 000000000000..e4fcc0de25e2
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/perf/arm,cmn.yaml
>> @@ -0,0 +1,57 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +# Copyright 2020 Arm Ltd.
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/perf/arm,cmn.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Arm CMN (Coherent Mesh Network) Performance Monitors
>> +
>> +maintainers:
>> + - Robin Murphy <robin.murphy@arm.com>
>> +
>> +properties:
>> + compatible:
>> + const: arm,cmn-600
>> +
>> + reg:
>> + items:
>> + - description: Physical address of the base (PERIPHBASE) and
>> + size (up to 64MB) of the configuration address space.
>> +
>> + interrupts:
>> + minItems: 1
>> + maxItems: 4
>> + items:
>> + - description: Overflow interrupt for DTC0
>> + - description: Overflow interrupt for DTC1
>> + - description: Overflow interrupt for DTC2
>> + - description: Overflow interrupt for DTC3
>> + description: One interrupt for each DTC domain implemented must
>> + be specified, in order. DTC0 is always present.
>
> What's DTC?
Debug and Trace Controller. I figure it's one of those situations where
if someone knows enough about a CMN configuration to be able to write
something to this binding, they're probably going to be familiar with
the abbreviation.
In CMN terminology, "DT" is all over the place meaning "Debug and
Trace". Only now do I suddenly realise that discussing this in the
context of Device Tree is pretty much the worst-case scenario for
confusion :)
>> +
>> + arm,root-node:
>> + $ref: /schemas/types.yaml#/definitions/uint32
>> + description: Offset from PERIPHBASE of the configuration
>> + discovery node (see TRM definition of ROOTNODEBASE).
>
> You can enforce some alignment:
>
> multipleOf: 0x4000
That's one of the things that may vary in future, so I'm doubtful if it
would really be worth the bother. There's only one correct value for a
given configuration, and still hundreds of appropriately-aligned wrong
ones, so ultimately either it's right and it works, or it's not and it
won't (any sensible driver should do a bit of sanity-checking during
discovery anyway).
Robin.
>> +
>> +required:
>> + - compatible
>> + - reg
>> + - interrupts
>> + - arm,root-node
>> +
>> +additionalProperties: false
>> +
>> +examples:
>> + - |
>> + #include <dt-bindings/interrupt-controller/arm-gic.h>
>> + #include <dt-bindings/interrupt-controller/irq.h>
>> + pmu@50000000 {
>> + compatible = "arm,cmn-600";
>> + reg = <0x50000000 0x4000000>;
>> + /* 4x2 mesh with one DTC, and CFG node at 0,1,1,0 */
>> + interrupts = <GIC_SPI 46 IRQ_TYPE_LEVEL_HIGH>;
>> + arm,root-node = <0x104000>;
>> + };
>> +...
>> --
>> 2.28.0.dirty
next prev parent reply other threads:[~2020-09-19 0:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 13:28 [PATCH v2 0/3] Arm CMN-600 PMU driver Robin Murphy
2020-09-18 13:28 ` [PATCH v2 1/3] perf: Add Arm CMN-600 DT binding Robin Murphy
2020-09-18 17:31 ` Rob Herring
2020-09-18 13:28 ` [PATCH v2 2/3] perf: Add Arm CMN-600 PMU driver Robin Murphy
2020-09-18 13:28 ` [RFC 3/3] perf/arm-cmn: Add debugfs topology info Robin Murphy
2020-09-18 18:24 ` [PATCH v2.1 1/3] perf: Add Arm CMN-600 DT binding Robin Murphy
2020-09-18 18:54 ` Rob Herring
2020-09-19 0:23 ` Robin Murphy [this message]
2020-10-05 9:16 ` [PATCH v2 0/3] Arm CMN-600 PMU driver Zidenberg, Tsahi
2020-10-05 10:21 ` Will Deacon
2020-10-14 16:31 ` Robin Murphy
2020-10-15 7:26 ` Zidenberg, Tsahi
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=152e2d42-9ace-f78b-145a-5882ce936c3e@arm.com \
--to=robin.murphy@arm.com \
--cc=alisaidi@amazon.com \
--cc=devicetree@vger.kernel.org \
--cc=harb@amperecomputing.com \
--cc=james.yang@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=patrik.berglund@arm.com \
--cc=robh@kernel.org \
--cc=tsahee@amazon.com \
--cc=tuanphan@os.amperecomputing.com \
--cc=will@kernel.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).