Devicetree
 help / color / mirror / Atom feed
From: Jinlong Mao <quic_jinlmao@quicinc.com>
To: Mike Leach <mike.leach@linaro.org>
Cc: Suzuki K Poulose <suzuki.poulose@arm.com>,
	James Clark <james.clark@arm.com>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	<coresight@lists.linaro.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-arm-msm@vger.kernel.org>,
	"Tingwei Zhang" <quic_tingweiz@quicinc.com>,
	Yuanfang Zhang <quic_yuanfang@quicinc.com>,
	Tao Zhang <quic_taozha@quicinc.com>,
	songchai <quic_songchai@quicinc.com>,
	Jie Gan <quic_jiegan@quicinc.com>
Subject: Re: [PATCH v4 0/2] coresight: core: Add device name support
Date: Fri, 18 Oct 2024 16:42:33 +0800	[thread overview]
Message-ID: <5dcce78a-d7e5-4a61-a165-05b9efe11052@quicinc.com> (raw)
In-Reply-To: <CAJ9a7VhwD6kFHPTgrfs+7fNx4nXZPqXTLK0ObmJM3A6mQfmuyQ@mail.gmail.com>



On 2024/7/31 23:15, Mike Leach wrote:
> Hi,
> 
> 1) As per Krzysztof comment - use the standard "label" property
> 
> 2) Do not use the label string as the node name - there is no
> guarantee of uniqueness which will cause issues. Please add the label
> as a sysfs file to the standard node.
> This uses the existing standard names, allowing any scripting based on
> this to continue to work, and will not cause issues with uniqueness
> 
> e.g.
> This will allow :
> 
> cat cti_cpu0/label
> 
> to extract the additional hardware context information that you need.
> 
> Thanks
> 
> Mike

Hi Mike,

I tried to get the label in the driver code. But I don't find any
function for it. Do you know the function to get the label of the device
tree node ?

label: node_name@node_address

Thanks
Jinlong Mao

> 
> 
> On Wed, 3 Jul 2024 at 13:24, Mao Jinlong <quic_jinlmao@quicinc.com> wrote:
>>
>> With current design, the name of the non-cpu bounded coresight
>> component is the device type with the number. And with 'ls' command
>> we can get the register address of the component. But from these
>> information, we can't know what the HW or system the component belongs
>> to. Add device-name in DT to support it.
>>
>> cti_sys0 -> ../../../devices/platform/soc@0/138f0000.cti/cti_sys0
>> cti_sys1 -> ../../../devices/platform/soc@0/13900000.cti/cti_sys1
>> tpdm0 -> ../../../devices/platform/soc@0/10b0d000.tpdm/tpdm0
>> tpdm1 -> ../../../devices/platform/soc@0/10c28000.tpdm/tpdm1
>> tpdm2 -> ../../../devices/platform/soc@0/10c29000.tpdm/tpdm2
>>
>> Change since V3:
>> 1. Change device-name to arm,cs-dev-name.
>> 2. Add arm,cs-dev-name to only CTI and sources' dt-binding.
>>
>> Change since V2:
>> 1. Fix the error in coresight core.
>> drivers/hwtracing/coresight/coresight-core.c:1775:7: error: assigning to 'char *' from 'const char *' discards qualifiers
>>
>> 2. Fix the warning when run dtbinding check.
>> Documentation/devicetree/bindings/arm/arm,coresight-cpu-debug.yaml: device-name: missing type definition
>>
>> Change since V1:
>> 1. Change coresight-name to device name.
>> 2. Add the device-name in coresight dt bindings.
>>
>>
>> Mao Jinlong (2):
>>    coresight: core: Add device name support
>>    dt-bindings: arm: Add device-name in the coresight components
>>
>>   .../bindings/arm/arm,coresight-catu.yaml      |  6 +++
>>   .../bindings/arm/arm,coresight-cpu-debug.yaml |  6 +++
>>   .../bindings/arm/arm,coresight-cti.yaml       |  6 +++
>>   .../arm/arm,coresight-dummy-sink.yaml         |  6 +++
>>   .../arm/arm,coresight-dummy-source.yaml       |  6 +++
>>   .../arm/arm,coresight-dynamic-funnel.yaml     |  6 +++
>>   .../arm/arm,coresight-dynamic-replicator.yaml |  6 +++
>>   .../bindings/arm/arm,coresight-etb10.yaml     |  6 +++
>>   .../bindings/arm/arm,coresight-etm.yaml       |  6 +++
>>   .../arm/arm,coresight-static-funnel.yaml      |  6 +++
>>   .../arm/arm,coresight-static-replicator.yaml  |  6 +++
>>   .../bindings/arm/arm,coresight-stm.yaml       |  6 +++
>>   .../bindings/arm/arm,coresight-tmc.yaml       |  6 +++
>>   .../bindings/arm/arm,coresight-tpiu.yaml      |  6 +++
>>   .../bindings/arm/qcom,coresight-tpda.yaml     |  6 +++
>>   .../bindings/arm/qcom,coresight-tpdm.yaml     |  6 +++
>>   drivers/hwtracing/coresight/coresight-core.c  | 37 ++++++++++---------
>>   .../hwtracing/coresight/coresight-platform.c  | 31 ++++++++++++++++
>>   include/linux/coresight.h                     |  3 +-
>>   19 files changed, 149 insertions(+), 18 deletions(-)
>>
>> Mao Jinlong (2):
>>    dt-bindings: arm: Add device-name in the coresight components
>>    coresight: core: Add device name support
>>
>>   .../bindings/arm/arm,coresight-cti.yaml       |  6 +++
>>   .../arm/arm,coresight-dummy-source.yaml       |  6 +++
>>   .../bindings/arm/arm,coresight-stm.yaml       |  6 +++
>>   .../bindings/arm/qcom,coresight-tpdm.yaml     |  6 +++
>>   drivers/hwtracing/coresight/coresight-core.c  | 37 ++++++++++---------
>>   .../hwtracing/coresight/coresight-platform.c  | 30 +++++++++++++++
>>   include/linux/coresight.h                     |  3 +-
>>   7 files changed, 76 insertions(+), 18 deletions(-)
>>
>> --
>> 2.41.0
>>
> 
> 
> --
> Mike Leach
> Principal Engineer, ARM Ltd.
> Manchester Design Centre. UK


  reply	other threads:[~2024-10-18  8:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-03 12:23 [PATCH v4 0/2] coresight: core: Add device name support Mao Jinlong
2024-07-03 12:23 ` [PATCH v4 1/2] dt-bindings: arm: Add device-name in the coresight components Mao Jinlong
2024-07-24 19:13   ` Krzysztof Kozlowski
2024-10-18 10:17     ` Suzuki K Poulose
2024-10-18 10:22       ` Krzysztof Kozlowski
2024-07-03 12:23 ` [PATCH v4 2/2] coresight: core: Add device name support Mao Jinlong
2024-07-31 15:15 ` [PATCH v4 0/2] " Mike Leach
2024-10-18  8:42   ` Jinlong Mao [this message]
2024-10-24 12:45     ` Mike Leach

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=5dcce78a-d7e5-4a61-a165-05b9efe11052@quicinc.com \
    --to=quic_jinlmao@quicinc.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=conor+dt@kernel.org \
    --cc=coresight@lists.linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=james.clark@arm.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=quic_jiegan@quicinc.com \
    --cc=quic_songchai@quicinc.com \
    --cc=quic_taozha@quicinc.com \
    --cc=quic_tingweiz@quicinc.com \
    --cc=quic_yuanfang@quicinc.com \
    --cc=robh@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