Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Hao Zhang <quic_hazha@quicinc.com>
To: Suzuki K Poulose <suzuki.poulose@arm.com>,
	Mathieu Poirier <mathieu.poirier@linaro.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Konrad Dybcio <konradybcio@gmail.com>,
	Mike Leach <mike.leach@linaro.org>,
	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: 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 v1 0/3] Add support to configure Coresight Dummy subunit
Date: Fri, 17 Mar 2023 15:40:54 +0800	[thread overview]
Message-ID: <4c2ff883-13af-19be-e4e2-35a66f2572fa@quicinc.com> (raw)
In-Reply-To: <0db33881-7978-41c9-45e3-63dc2ed7be4f@arm.com>

Hi Suzuki,

On 3/16/2023 6:55 PM, Suzuki K Poulose wrote:
> On 16/03/2023 03:20, 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
> 
> What is HLOS ?

The term HLOS stands for High Level OS, it means linux in this case. The 
HLOS runs on APPS processor.

>> some TPDMs, they would be configured in NON-HLOS side, but it's 
>> necessary to
> 
> What is NON-HLOS ?

There are some other sub-processors like modem, adsp etc, they do not 
have a High Level OS. The OS in these sub-processors is lightweight, 
less powerful, somewhat real-time, it would be called NON-HLOS.

>> build Coresight path for it to debug. So there need driver to register 
>> dummy
>> devices as Coresight devices.
> 
> Build a path for who to debug ? If this is used by some privileged
> software, shouldn't that do all of the work ?
> 
> Suzuki

There is coresight source or sink in sub-processor, it would be 
configured by NON-HLOS, and need HLOS to configure the last coresight 
components. So we will use dummy source or sink to replace it in HLOS 
side for building the whole path(from source to sink).

Thanks,
Hao

>>
>> Commit link:
>> https://git.codelinaro.org/clo/linux-kernel/coresight/-/tree/coresight-dummy
>>
>> Hao Zhang (3):
>>    Coresight: Add coresight dummy driver
>>    dt-bindings: arm: Add Coresight Dummy Trace YAML schema
>>    Documentation: trace: Add documentation for Coresight Dummy Trace
>>
>>   .../bindings/arm/qcom,coresight-dummy.yaml    | 129 +++++++++++++
>>   .../trace/coresight/coresight-dummy.rst       |  58 ++++++
>>   drivers/hwtracing/coresight/Kconfig           |  11 ++
>>   drivers/hwtracing/coresight/Makefile          |   1 +
>>   drivers/hwtracing/coresight/coresight-dummy.c | 176 ++++++++++++++++++
>>   5 files changed, 375 insertions(+)
>>   create mode 100644 
>> Documentation/devicetree/bindings/arm/qcom,coresight-dummy.yaml
>>   create mode 100644 Documentation/trace/coresight/coresight-dummy.rst
>>   create mode 100644 drivers/hwtracing/coresight/coresight-dummy.c
>>
> 

      reply	other threads:[~2023-03-17  7:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-16  3:20 [PATCH v1 0/3] Add support to configure Coresight Dummy subunit Hao Zhang
2023-03-16  3:20 ` [PATCH v1 1/3] Coresight: Add coresight dummy driver Hao Zhang
2023-03-16  9:32   ` kernel test robot
2023-03-16  3:20 ` [PATCH v1 2/3] dt-bindings: arm: Add Coresight Dummy Trace YAML schema Hao Zhang
2023-03-16 13:53   ` Rob Herring
2023-03-17  8:19     ` Hao Zhang
2023-03-16  3:20 ` [PATCH v1 3/3] Documentation: trace: Add documentation for Coresight Dummy Trace Hao Zhang
2023-03-16 10:55 ` [PATCH v1 0/3] Add support to configure Coresight Dummy subunit Suzuki K Poulose
2023-03-17  7:40   ` Hao Zhang [this message]

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=4c2ff883-13af-19be-e4e2-35a66f2572fa@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=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