linux-kernel - Re: [PATCH v2 0/2] coresight: core: Add device name support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <cef041b7-70ac-47c9-888c-696a0cec04d1@arm.com>
Date: Tue, 16 Jan 2024 13:43:49 +0000
From: Suzuki K Poulose <suzuki.poulose@....com>
To: Mao Jinlong <quic_jinlmao@...cinc.com>, Mike Leach
 <mike.leach@...aro.org>, James Clark <james.clark@....com>,
 Leo Yan <leo.yan@...aro.org>,
 Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
 Rob Herring <robh+dt@...nel.org>,
 Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
 Conor Dooley <conor+dt@...nel.org>,
 Maxime Coquelin <mcoquelin.stm32@...il.com>,
 Alexandre Torgue <alexandre.torgue@...s.st.com>,
 Bjorn Andersson <andersson@...nel.org>,
 Konrad Dybcio <konrad.dybcio@...aro.org>,
 Mathieu Poirier <mathieu.poirier@...aro.org>
Cc: coresight@...ts.linaro.org, linux-arm-kernel@...ts.infradead.org,
 linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
 linux-stm32@...md-mailman.stormreply.com, linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH v2 0/2] coresight: core: Add device name support

On 15/01/2024 16:42, Mao Jinlong 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@...38f0000.cti/cti_sys0
> cti_sys1 -> ../../../devices/platform/soc@...3900000.cti/cti_sys1
> tpdm0 -> ../../../devices/platform/soc@...0b0d000.tpdm/tpdm0
> tpdm1 -> ../../../devices/platform/soc@...0c28000.tpdm/tpdm1
> tpdm2 -> ../../../devices/platform/soc@...0c29000.tpdm/tpdm2

Please could you rebase this on for-next/queue (which has all bells and 
whistles enabled to report Warnings), fixing the reported issue by 
kernel test robot ?

Suzuki


> 
> 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      |  5 +++
>   .../bindings/arm/arm,coresight-cpu-debug.yaml |  5 +++
>   .../bindings/arm/arm,coresight-cti.yaml       |  5 +++
>   .../arm/arm,coresight-dummy-sink.yaml         |  5 +++
>   .../arm/arm,coresight-dummy-source.yaml       |  5 +++
>   .../arm/arm,coresight-dynamic-funnel.yaml     |  5 +++
>   .../arm/arm,coresight-dynamic-replicator.yaml |  5 +++
>   .../bindings/arm/arm,coresight-etb10.yaml     |  5 +++
>   .../bindings/arm/arm,coresight-etm.yaml       |  5 +++
>   .../arm/arm,coresight-static-funnel.yaml      |  5 +++
>   .../arm/arm,coresight-static-replicator.yaml  |  5 +++
>   .../bindings/arm/arm,coresight-stm.yaml       |  5 +++
>   .../bindings/arm/arm,coresight-tmc.yaml       |  5 +++
>   .../bindings/arm/arm,coresight-tpiu.yaml      |  5 +++
>   .../bindings/arm/qcom,coresight-tpda.yaml     |  5 +++
>   .../bindings/arm/qcom,coresight-tpdm.yaml     |  5 +++
>   drivers/hwtracing/coresight/coresight-core.c  | 33 ++++++++++---------
>   .../hwtracing/coresight/coresight-platform.c  | 31 +++++++++++++++++
>   include/linux/coresight.h                     |  1 +
>   19 files changed, 130 insertions(+), 15 deletions(-)
>