From: Hao Zhang <quic_hazha@quicinc.com>
To: Suzuki K Poulose <suzuki.poulose@arm.com>,
Mike Leach <mike.leach@linaro.org>, Leo Yan <leo.yan@linaro.org>,
James Clark <james.clark@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Konrad Dybcio <konradybcio@gmail.com>,
"Rob Herring" <robh+dt@kernel.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>
Cc: 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 v5 0/3] Add support to configure Coresight Dummy subunit
Date: Mon, 29 May 2023 15:17:32 +0800 [thread overview]
Message-ID: <5c56a874-dc41-c68c-6f70-efcbc67c29b2@quicinc.com> (raw)
In-Reply-To: <20230526100753.34581-1-quic_hazha@quicinc.com>
Hi,
Add the missing information for this patch series.
Thanks,
Hao
On 5/26/2023 6:07 PM, Hao Zhang wrote:
Introduction of Coresight Dummy subunit
The Coresight Dummy subunit is for Coresight Dummy component, there are
some specific Coresight devices that HLOS don't have permission to access.
Such as some TPDMs, they would be configured in NON-HLOS side, but it's
necessary to build Coresight path for it to debug. So there need driver
to register dummy devices as Coresight devices.
Commit link:
https://git.codelinaro.org/clo/linux-kernel/coresight/-/tree/coresight-dummy-v5
> Changes in V5:
> 1. Follow the alphabetical order for the header files in
> coresight-dummy.c. -- Suzuki K Poulose
> 2. Update the maintainers.
> 3. Split the Coresight Dummy YAML to 2 schema files.
> -- Rob Herring & Krzysztof Kozlowski
> 4. Update the coresight-dummy.rst file. -- Bagas Sanjaya
>
> Changes in V4:
> 1. Remove traceid allocation in dummy_probe function since it is
> currently not in use, will upstream it as the part of ATID filtering
> in the further. -- Suzuki K Poulose
> 2. Remove 'oneOf' as there is only one entry. -- Rob Herring
>
> Changes in V3:
> 1. Use API "dev_dbg" to replace "dev_info". -- Suzuki K Poulose
> 2. Drop "qcom" property and take it as a dummy framework.
> -- Suzuki K Poulose
> 3. Add new sub-type "CORESIGHT_DEV_SUBTYPE_SINK_DUMMY" to support
> coresight dummy module -- Mike Leach
> 4. Use compatibles "arm,coresight-dummy-source" and
> "arm,coresight-dummy-sink" to replace property "qcom,dummy-source" and
> "qcom,dummy-sink". -- Mike Leach
> 5. Define source_devs and sink_devs DEVLIST to replace dummy_devs, make
> it clear at the first level. -- Mike Leach
> 6. Modify subject of YAML patch, drop "YAML schema". -- Krzysztof Kozlowski
> 7. Drop some redundant items and correct syntax errors in yaml file.
> -- Krzysztof Kozlowski & Rob Herring
> 8. Correct required property of yaml file, constrain out ports to
> dummy-source and in ports to dummy-sink. -- Mike Leach
> 9. Drop "Sysfs files and directories" contents of coresight-dummy.rst.
> -- Suzuki K Poulose/Greg Kroah-Hartman
> 10.Correct syntax errors of coresight-dummy.rst. -- Bagas Sanjaya
>
> Changes in V2:
> 1. Declare dummy_init and dummy_exit as static to fix missing-prototypes
> warnings. -- kernel test robot
> 2. Fix the errors of coresight-dummy yaml file. -- Rob Herring
>
> Hao Zhang (3):
> Coresight: Add coresight dummy driver
> dt-bindings: arm: Add support for Coresight dummy trace
> Documentation: trace: Add documentation for Coresight Dummy Trace
>
> .../arm/arm,coresight-dummy-sink.yaml | 73 ++++++++
> .../arm/arm,coresight-dummy-source.yaml | 71 ++++++++
> .../trace/coresight/coresight-dummy.rst | 32 ++++
> drivers/hwtracing/coresight/Kconfig | 11 ++
> drivers/hwtracing/coresight/Makefile | 1 +
> drivers/hwtracing/coresight/coresight-dummy.c | 163 ++++++++++++++++++
> include/linux/coresight.h | 1 +
> 7 files changed, 352 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/arm/arm,coresight-dummy-sink.yaml
> create mode 100644 Documentation/devicetree/bindings/arm/arm,coresight-dummy-source.yaml
> create mode 100644 Documentation/trace/coresight/coresight-dummy.rst
> create mode 100644 drivers/hwtracing/coresight/coresight-dummy.c
>
next prev parent reply other threads:[~2023-05-29 7:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 10:07 Hao Zhang
2023-05-26 10:07 ` [PATCH v5 1/3] Coresight: Add coresight dummy driver Hao Zhang
2023-05-26 10:07 ` [PATCH v5 2/3] dt-bindings: arm: Add support for Coresight dummy trace Hao Zhang
2023-05-26 10:07 ` [PATCH v5 3/3] Documentation: trace: Add documentation for Coresight Dummy Trace Hao Zhang
2023-05-29 7:28 ` Bagas Sanjaya
2023-05-29 7:17 ` Hao Zhang [this message]
2023-05-29 8:11 ` [PATCH v5 0/3] Add support to configure Coresight Dummy subunit Bagas Sanjaya
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=5c56a874-dc41-c68c-6f70-efcbc67c29b2@quicinc.com \
--to=quic_hazha@quicinc.com \
--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=james.clark@arm.com \
--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_jinlmao@quicinc.com \
--cc=quic_taozha@quicinc.com \
--cc=quic_tingweiz@quicinc.com \
--cc=quic_tsoni@quicinc.com \
--cc=quic_yuanfang@quicinc.com \
--cc=robh+dt@kernel.org \
--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
all inboxes | Powered by JetHome®