linux-kernel - [PATCH 0/4] Add support for multi-port output on the funnel

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-next>] [day] [month] [year] [list]

Message-ID: <1711009927-17873-1-git-send-email-quic_taozha@quicinc.com>
Date: Thu, 21 Mar 2024 16:32:03 +0800
From: Tao Zhang <quic_taozha@...cinc.com>
To: Mathieu Poirier <mathieu.poirier@...aro.org>,
        Suzuki K Poulose
	<suzuki.poulose@....com>,
        Alexander Shishkin
	<alexander.shishkin@...ux.intel.com>,
        Konrad Dybcio <konradybcio@...il.com>,
        Mike Leach <mike.leach@...aro.org>, Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>
CC: Tao Zhang <quic_taozha@...cinc.com>,
        Jinlong Mao
	<quic_jinlmao@...cinc.com>, Leo Yan <leo.yan@...aro.org>,
        Greg Kroah-Hartman
	<gregkh@...uxfoundation.org>,
        <coresight@...ts.linaro.org>, <linux-arm-kernel@...ts.infradead.org>,
        <linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>,
        Tingwei Zhang <quic_tingweiz@...cinc.com>,
        Yuanfang Zhang <quic_yuanfang@...cinc.com>,
        Trilok Soni
	<quic_tsoni@...cinc.com>,
        Song Chai <quic_songchai@...cinc.com>, <linux-arm-msm@...r.kernel.org>,
        <andersson@...nel.org>
Subject: [PATCH 0/4] Add support for multi-port output on the funnel

Funnel can support multi-port output in our hardware design. Since original
funnels only support a single output connection, the code needs to be
modified to support this new feature. The following is a typical topology
diagram of multi-port output of the funnels.
|---------|    |---------|    |---------|    |---------|    |---------|
|  TPDM0  |    |  TPDM1  |    |  TPDM2  |    |  TPDM3  |    |  TPDM4  |
|---------|    |---------|    |---------|    |---------|    |---------|
    |               |             |               |              |
    |               |             |               |              |
    |               |             |               |              |
    |-----|   |-----|             |-----|   |-----|              |
          |   |                         |   |                    |
          |   |                         |   |                    |
       [0]|   |[1]                   [0]|   |[1]                 |
     \-------------/               \-------------/        \-------------/
      \  FUNNEL0  /                 \  FUNNEL1  /          \  FUNNEL2  /
       -----------                   -----------            -----------
       [0]|  |[1]                   [0]|   |[1]                  |
          |  |----------               |   |                     |
          |            |               |   |                     |
          |-------|    |      |------- |   |          |--------- |
                  |    |      |            |          |
                  |    |      |            |          |
               [0]|    |[1]   |[2]         |[3]       |[4]
           \ ---------------------------------------------------/
            \                     TPDA0                        /
             \                                                /
              ------------------------------------------------
For example, TPDM0 and TPDM1 are connected to the [0] and [1] input ports
of the funnel respectively, and output from the [0] and [1] output ports.
In this way, when data is output from the Funnel's output port, it needs
to know the source component corresponding to this output port. Our
solution is to add a property named "label" in the devicetree to mark the
source corresponding to the output port.
After introducing this new feature, another new problem also needs to be
solved. For example, TPDA driver will search for all the TPDMs on a input
port. In the topology diagram above, when TPDA searches for TPDM from the
input port[0], it will find TPDM0 and TPDM1. Our solution is to add a new
property named "qcom,tpda-input-port" to mark the input port number of the
TPDA in the devicetree.

Tao Zhang (4):
  dt-bindings: arm: qcom,coresight-funnel: Add label for multi-ouput
  coresight: Add support for multiple output ports on the funnel
  dt-bindings: arm: qcom,coresight-tpdm: Mark tpda input port number
  coresight-tpda: Add support multi-port input on TPDA

 .../arm/arm,coresight-dynamic-funnel.yaml     | 34 +++++++-
 .../bindings/arm/qcom,coresight-tpdm.yaml     |  8 ++
 drivers/hwtracing/coresight/coresight-core.c  | 81 ++++++++++++++++---
 .../hwtracing/coresight/coresight-platform.c  |  5 ++
 drivers/hwtracing/coresight/coresight-tpda.c  | 27 ++++++-
 include/linux/coresight.h                     |  2 +
 6 files changed, 139 insertions(+), 18 deletions(-)

-- 
2.17.1