From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Mao Jinlong <quic_jinlmao@quicinc.com>,
Mike Leach <mike.leach@linaro.org>,
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>
Cc: 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 1/2] dt-bindings: arm: Add device-name in the coresight components
Date: Fri, 18 Oct 2024 11:17:54 +0100 [thread overview]
Message-ID: <a82cd3f2-a8ba-4f19-820d-509dc45f74c1@arm.com> (raw)
In-Reply-To: <980422ea-8c44-47a4-8996-8653bab3ef8a@kernel.org>
On 24/07/2024 20:13, Krzysztof Kozlowski wrote:
> On 03/07/2024 14:23, Mao Jinlong wrote:
>> Current name of coresight component's folder consists of prefix of
>> the device and the id in the device list. When run 'ls' command,
>> we can get the register address of the device. Take CTI for example,
>> if we want to set the config for modem CTI, but we can't know which
>> CTI is modem CTI from all current information.
>>
>> cti_sys0 -> ../../../devices/platform/soc@0/138f0000.cti/cti_sys0
>> cti_sys1 -> ../../../devices/platform/soc@0/13900000.cti/cti_sys1
>>
>> Add device-name in device tree which can provide a better description
>> of the coresight device. It can provide the info like the system or
>> HW it belongs to.
>>
>> Signed-off-by: Mao Jinlong <quic_jinlmao@quicinc.com>
>> ---
>> .../devicetree/bindings/arm/arm,coresight-cti.yaml | 6 ++++++
>> .../devicetree/bindings/arm/arm,coresight-dummy-source.yaml | 6 ++++++
>> .../devicetree/bindings/arm/arm,coresight-stm.yaml | 6 ++++++
>> .../devicetree/bindings/arm/qcom,coresight-tpdm.yaml | 6 ++++++
>> 4 files changed, 24 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/arm/arm,coresight-cti.yaml b/Documentation/devicetree/bindings/arm/arm,coresight-cti.yaml
>> index 2d5545a2b49c..6a73eaa66a42 100644
>> --- a/Documentation/devicetree/bindings/arm/arm,coresight-cti.yaml
>> +++ b/Documentation/devicetree/bindings/arm/arm,coresight-cti.yaml
>> @@ -98,6 +98,12 @@ properties:
>> power-domains:
>> maxItems: 1
>>
>> + arm,cs-dev-name:
>> + $ref: /schemas/types.yaml#/definitions/string
>> + description:
>> + Define the name which can describe what kind of HW or system the
>> + coresight device belongs to.
>
> Don't we use already label for such cases? Power domains, input, leds,
> panels, IIO, hwmon and more.
We do and if we can get hold of them, that would be ideal. but do we get
them in the binary DT blob ? At least I couldn't see them on my Juno
dtb.
Cheers
Suzuki
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2024-10-18 10:17 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 [this message]
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
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=a82cd3f2-a8ba-4f19-820d-509dc45f74c1@arm.com \
--to=suzuki.poulose@arm.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=krzk@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_jinlmao@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 \
/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