From: Krzysztof Kozlowski <krzk@kernel.org>
To: Yuanfang Zhang <yuanfang.zhang@oss.qualcomm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Mike Leach <mike.leach@linaro.org>,
James Clark <james.clark@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: kernel@oss.qualcomm.com, coresight@lists.linaro.org,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: arm: qcom: Add Coresight Interconnect TNOC
Date: Sat, 16 Aug 2025 10:33:34 +0200 [thread overview]
Message-ID: <e82ca132-f312-45b5-bec0-9d83cd3771d4@kernel.org> (raw)
In-Reply-To: <20250815-itnoc-v1-1-62c8e4f7ad32@oss.qualcomm.com>
On 15/08/2025 15:18, Yuanfang Zhang wrote:
> Add device tree binding for Qualcomm Coresight Interconnect Trace
> Netwrok On Chip (ITNOC). This TNOC acts as a CoreSight
> graph link that forwards trace data from a subsystem to the
> Aggregator TNOC, without aggregation or ATID functionality.
>
> Signed-off-by: Yuanfang Zhang <yuanfang.zhang@oss.qualcomm.com>
> ---
> .../bindings/arm/qcom,coresight-itnoc.yaml | 108 +++++++++++++++++++++
> 1 file changed, 108 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/qcom,coresight-itnoc.yaml b/Documentation/devicetree/bindings/arm/qcom,coresight-itnoc.yaml
> new file mode 100644
> index 0000000000000000000000000000000000000000..fd224e07ce68918b453210763aacda585d5a5ca2
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/qcom,coresight-itnoc.yaml
> @@ -0,0 +1,108 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/arm/qcom,coresight-itnoc.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Qualcomm Interconnect Trace Network On Chip - ITNOC
> +
> +maintainers:
> + - Yuanfang Zhang <yuanfang.zhang@oss.qualcomm.com>
> +
> +description: |
Do not need '|' unless you need to preserve formatting.
> + The Interconnect TNOC is a CoreSight graph link that forwards trace data
> + from a subsystem to the Aggregator TNOC. Compared to Aggregator TNOC, it
> + does not have aggregation and ATID functionality.
> +
> +select:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - qcom,coresight-itnoc
> + required:
> + - compatible
Why all this? Drop
> +
> +properties:
> + $nodename:
> + pattern: "^tnoc(@[0-9a-f]+)?$"
Why are you requiring a non-generic name?
> +
> + compatible:
> + items:
No need for items
> + - const: qcom,coresight-itnoc
> +
> + reg:
> + maxItems: 1
> + description: Base address and size of the ITNOC registers.
Drop, redundant
> +
> + clock-names:
> + items:
> + - const: apb
Drop clock-names, obvious. Also, odd order - names are never before
actual property.
> +
> + clocks:
> + maxItems: 1
> +
> + in-ports:
> + $ref: /schemas/graph.yaml#/properties/ports
> +
> + properties:
> + '#address-cells':
> + const: 1
> + '#size-cells':
> + const: 0
> +
> + patternProperties:
> + '^port(@[0-9a-f]{1,2})?$':
Why do you have here 255 ports?
> + description: Input connections from CoreSight Trace Bus
> + $ref: /schemas/graph.yaml#/properties/port
> + additionalProperties: false
This goes after $ref
> +
> + out-ports:
> + $ref: /schemas/graph.yaml#/properties/ports
> +
> + properties:
> + port:
> + description: out connections to aggregator TNOC
> + $ref: /schemas/graph.yaml#/properties/port
> + additionalProperties: false
This goes after ref
> +
> +required:
> + - compatible
> + - reg
> + - clocks
> + - clock-names
And here different order... Be consistent. See also DTS coding style.
> + - in-ports
> + - out-ports
> +
> +additionalProperties: false
> +
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-08-16 8:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 13:18 [PATCH 0/3] coresight-tnoc: Add support for Interconnect TNOC Yuanfang Zhang
2025-08-15 13:18 ` [PATCH 1/3] dt-bindings: arm: qcom: Add Coresight " Yuanfang Zhang
2025-08-16 8:33 ` Krzysztof Kozlowski [this message]
2025-08-18 9:29 ` yuanfang zhang
2025-08-15 13:18 ` [PATCH 2/3] coresight-tnoc: add platform driver to support " Yuanfang Zhang
2025-08-18 14:27 ` Leo Yan
2025-08-19 7:31 ` yuanfang zhang
2025-08-15 13:18 ` [PATCH 3/3] coresight-tnoc: Add runtime PM support for " Yuanfang Zhang
2025-08-18 14:30 ` Leo Yan
2025-08-19 7:32 ` yuanfang zhang
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=e82ca132-f312-45b5-bec0-9d83cd3771d4@kernel.org \
--to=krzk@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=conor+dt@kernel.org \
--cc=coresight@lists.linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=james.clark@linaro.org \
--cc=kernel@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.leach@linaro.org \
--cc=robh@kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=yuanfang.zhang@oss.qualcomm.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;
as well as URLs for NNTP newsgroup(s).