From: Rob Herring <robh@kernel.org>
To: Hao Zhang <quic_hazha@quicinc.com>
Cc: Mathieu Poirier <mathieu.poirier@linaro.org>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Konrad Dybcio <konradybcio@gmail.com>,
Mike Leach <mike.leach@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Andy Gross <agross@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Jonathan Corbet <corbet@lwn.net>, Leo Yan <leo.yan@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Tingwei Zhang <quic_tingweiz@quicinc.com>,
Jinlong Mao <quic_jinlmao@quicinc.com>,
Yuanfang Zhang <quic_yuanfang@quicinc.com>,
Tao Zhang <quic_taozha@quicinc.com>,
Trilok Soni <quic_tsoni@quicinc.com>,
linux-arm-msm@vger.kernel.org,
Bjorn Andersson <andersson@kernel.org>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v2 2/3] dt-bindings: arm: Add Coresight Dummy Trace YAML schema
Date: Fri, 31 Mar 2023 13:47:00 -0500 [thread overview]
Message-ID: <20230331184700.GA1920623-robh@kernel.org> (raw)
In-Reply-To: <20230324061608.33609-3-quic_hazha@quicinc.com>
On Fri, Mar 24, 2023 at 02:16:07PM +0800, Hao Zhang wrote:
> Add new coresight-dummy.yaml file describing the bindings required
> to define coresight dummy trace in the device trees.
The diff tells me all this. Please explain why this is needed and needs
to be in DT here.
>
> Signed-off-by: Hao Zhang <quic_hazha@quicinc.com>
> ---
> .../bindings/arm/qcom,coresight-dummy.yaml | 118 ++++++++++++++++++
> 1 file changed, 118 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/arm/qcom,coresight-dummy.yaml
>
> diff --git a/Documentation/devicetree/bindings/arm/qcom,coresight-dummy.yaml b/Documentation/devicetree/bindings/arm/qcom,coresight-dummy.yaml
> new file mode 100644
> index 000000000000..7b719b084d72
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/qcom,coresight-dummy.yaml
> @@ -0,0 +1,118 @@
> +# SPDX-License-Identifier: GPL-2.0-only or BSD-2-Clause
> +# Copyright (c) 2023 Qualcomm Innovation Center, Inc. All rights reserved.
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/arm/qcom,coresight-dummy.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: QCOM Coresight Dummy component
> +
> +description: |
> + The Coresight Dummy component is for the specific devices that HLOS don't have
> + permission to access or configure. Such as Coresight sink EUD, some TPDMs etc.
EUD? TPDM?
I don't really love 'dummy' used here. Maybe the OS still wants/needs to
know where the sink goes to even if not configurable.
You *can* have multiple compatibles for a single generic driver if those
compatibles might be useful some day.
> + So there need driver to register dummy devices as Coresight devices. Provide
> + Coresight API for dummy device operations, such as enabling and disabling
> + dummy devices. Build the Coresight path for dummy sink or dummy source for
> + debugging.
> +
> + The primary use case of the coresight dummy is to build path for dummy sink or
> + dummy source.
> +
> +maintainers:
> + - Mao Jinlong <quic_jinlmao@quicinc.com>
> + - Tao Zhang <quic_taozha@quicinc.com>
> + - Hao Zhang <quic_hazha@quicinc.com>
> +
> +select:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - qcom,coresight-dummy
> + required:
> + - compatible
> +
> +properties:
> + $nodename:
> + pattern: "^dummy_.*(sink|source)_[0-9]+.*$"
Don't use '_' in node names.
Convention for multiple instances without 'reg' is '-[0-9]+' on the end,
but you are allowing anything after that.
> + compatible:
> + items:
> + - const: qcom,coresight-dummy
> +
> + qcom,dummy-sink:
> + type: boolean
> + description:
> + Indicates that the type of this coresight node is dummy sink.
> +
> + qcom,dummy-source:
Incorporate source or sink into the compatible strings.
It's also somewhat redundant with 'in-ports' vs. 'out-ports'.
> + type: boolean
> + description:
> + Indicates that the type of this coresight node is dummy source.
> +
> + out-ports:
> + description: |
Don't need '|' unless you need to preserve formatting.
> + Output connections from the dummy source to Coresight Trace bus.
> + $ref: /schemas/graph.yaml#/properties/ports
> +
> + properties:
> + port:
> + description: Output connection from the dummy source to Coresight
> + Trace bus.
> + $ref: /schemas/graph.yaml#/properties/port
> +
> + in-ports:
> + description: |
> + Input connections from the CoreSight Trace bus to dummy sink.
> + $ref: /schemas/graph.yaml#/properties/ports
> +
> + properties:
> + port:
> + description: Input connection from the Coresight Trace bus to
> + dummy sink.
> + $ref: /schemas/graph.yaml#/properties/port
> +
> +required:
> + - compatible
> +
> +additionalProperties: false
> +
> +oneOf:
> + - required:
> + - qcom,dummy-sink
> + - required:
> + - qcom,dummy-source
> +
> +examples:
> + # minimum dummy sink definition. dummy sink connect to coresight replicator.
> + - |
> + dummy_sink_1 {
> + compatible = "qcom,coresight-dummy";
> + qcom,dummy-sink;
> +
> + in-ports {
> + port {
> + eud_in_replicator_swao: endpoint {
> + remote-endpoint =
> + <&replicator_swao_out_eud>;
> + };
> + };
> + };
> + };
> +
> + # minimum dummy source definition. dummy source connect to coresight funnel.
> + - |
> + dummy_source_1 {
> + compatible = "qcom,coresight-dummy";
> + qcom,dummy-source;
> +
> + out-ports {
> + port {
> + dummy_riscv_out_funnel_swao: endpoint {
> + remote-endpoint =
> + <&funnel_swao_in_dummy_riscv>;
> + };
> + };
> + };
> + };
> +
> +...
> --
> 2.17.1
>
next prev parent reply other threads:[~2023-03-31 18:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 6:16 [PATCH v2 0/3] Add support to configure Coresight Dummy subunit Hao Zhang
2023-03-24 6:16 ` [PATCH v2 1/3] Coresight: Add coresight dummy driver Hao Zhang
2023-03-24 10:44 ` Suzuki K Poulose
2023-03-27 5:43 ` Hao Zhang
2023-03-27 15:58 ` Mike Leach
2023-03-28 7:22 ` Hao Zhang
2023-03-28 8:35 ` Suzuki K Poulose
2023-03-28 9:24 ` Hao Zhang
2023-03-28 10:06 ` Mike Leach
2023-03-28 11:25 ` Hao Zhang
2023-03-28 12:21 ` Suzuki K Poulose
2023-03-28 14:32 ` Mike Leach
2023-03-24 6:16 ` [PATCH v2 2/3] dt-bindings: arm: Add Coresight Dummy Trace YAML schema Hao Zhang
2023-03-24 10:47 ` Suzuki K Poulose
2023-03-27 5:58 ` Hao Zhang
2023-03-25 11:49 ` Krzysztof Kozlowski
2023-03-27 7:38 ` Hao Zhang
2023-03-28 10:12 ` Mike Leach
2023-03-28 11:29 ` Hao Zhang
2023-03-31 18:47 ` Rob Herring [this message]
2023-04-07 6:23 ` Hao Zhang
2023-03-24 6:16 ` [PATCH v2 3/3] Documentation: trace: Add documentation for Coresight Dummy Trace Hao Zhang
2023-03-24 11:00 ` Suzuki K Poulose
2023-03-27 6:05 ` Hao Zhang
2023-03-27 9:06 ` Bagas Sanjaya
2023-03-28 8:07 ` Hao Zhang
2023-03-27 9:13 ` Greg Kroah-Hartman
2023-03-28 1:45 ` Hao 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=20230331184700.GA1920623-robh@kernel.org \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=andersson@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=corbet@lwn.net \
--cc=coresight@lists.linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=konradybcio@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=quic_hazha@quicinc.com \
--cc=quic_jinlmao@quicinc.com \
--cc=quic_taozha@quicinc.com \
--cc=quic_tingweiz@quicinc.com \
--cc=quic_tsoni@quicinc.com \
--cc=quic_yuanfang@quicinc.com \
--cc=suzuki.poulose@arm.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).