1aa1a8ff2SEmmanuel Vadot# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 2f126890aSEmmanuel Vadot%YAML 1.2 3f126890aSEmmanuel Vadot--- 4f126890aSEmmanuel Vadot$id: http://devicetree.org/schemas/arm/arm,coresight-dummy-source.yaml# 5f126890aSEmmanuel Vadot$schema: http://devicetree.org/meta-schemas/core.yaml# 6f126890aSEmmanuel Vadot 7f126890aSEmmanuel Vadottitle: ARM Coresight Dummy source component 8f126890aSEmmanuel Vadot 9f126890aSEmmanuel Vadotdescription: | 10f126890aSEmmanuel Vadot CoreSight components are compliant with the ARM CoreSight architecture 11f126890aSEmmanuel Vadot specification and can be connected in various topologies to suit a particular 12f126890aSEmmanuel Vadot SoCs tracing needs. These trace components can generally be classified as 13f126890aSEmmanuel Vadot sinks, links and sources. Trace data produced by one or more sources flows 14f126890aSEmmanuel Vadot through the intermediate links connecting the source to the currently selected 15f126890aSEmmanuel Vadot sink. 16f126890aSEmmanuel Vadot 17f126890aSEmmanuel Vadot The Coresight dummy source component is for the specific coresight source 18f126890aSEmmanuel Vadot devices kernel don't have permission to access or configure. For some SOCs, 19f126890aSEmmanuel Vadot there would be Coresight source trace components on sub-processor which 20*b2d2a78aSEmmanuel Vadot are connected to AP processor via debug bus. For these devices, a dummy driver 21f126890aSEmmanuel Vadot is needed to register them as Coresight source devices, so that paths can be 22f126890aSEmmanuel Vadot created in the driver. It provides Coresight API for operations on dummy 23f126890aSEmmanuel Vadot source devices, such as enabling and disabling them. It also provides the 24f126890aSEmmanuel Vadot Coresight dummy source paths for debugging. 25f126890aSEmmanuel Vadot 26f126890aSEmmanuel Vadot The primary use case of the coresight dummy source is to build path in kernel 27f126890aSEmmanuel Vadot side for dummy source component. 28f126890aSEmmanuel Vadot 29f126890aSEmmanuel Vadotmaintainers: 30f126890aSEmmanuel Vadot - Mike Leach <mike.leach@linaro.org> 31f126890aSEmmanuel Vadot - Suzuki K Poulose <suzuki.poulose@arm.com> 320e8011faSEmmanuel Vadot - James Clark <james.clark@linaro.org> 33f126890aSEmmanuel Vadot - Mao Jinlong <quic_jinlmao@quicinc.com> 34f126890aSEmmanuel Vadot - Hao Zhang <quic_hazha@quicinc.com> 35f126890aSEmmanuel Vadot 36f126890aSEmmanuel Vadotproperties: 37f126890aSEmmanuel Vadot compatible: 38f126890aSEmmanuel Vadot enum: 39f126890aSEmmanuel Vadot - arm,coresight-dummy-source 40f126890aSEmmanuel Vadot 41f126890aSEmmanuel Vadot out-ports: 42f126890aSEmmanuel Vadot $ref: /schemas/graph.yaml#/properties/ports 43f126890aSEmmanuel Vadot 44f126890aSEmmanuel Vadot properties: 45f126890aSEmmanuel Vadot port: 46f126890aSEmmanuel Vadot description: Output connection from the source to Coresight 47f126890aSEmmanuel Vadot Trace bus. 48f126890aSEmmanuel Vadot $ref: /schemas/graph.yaml#/properties/port 49f126890aSEmmanuel Vadot 50f126890aSEmmanuel Vadotrequired: 51f126890aSEmmanuel Vadot - compatible 52f126890aSEmmanuel Vadot - out-ports 53f126890aSEmmanuel Vadot 54f126890aSEmmanuel VadotadditionalProperties: false 55f126890aSEmmanuel Vadot 56f126890aSEmmanuel Vadotexamples: 57f126890aSEmmanuel Vadot # Minimum dummy source definition. Dummy source connect to coresight funnel. 58f126890aSEmmanuel Vadot - | 59f126890aSEmmanuel Vadot source { 60f126890aSEmmanuel Vadot compatible = "arm,coresight-dummy-source"; 61f126890aSEmmanuel Vadot 62f126890aSEmmanuel Vadot out-ports { 63f126890aSEmmanuel Vadot port { 64f126890aSEmmanuel Vadot dummy_riscv_out_funnel_swao: endpoint { 65f126890aSEmmanuel Vadot remote-endpoint = <&funnel_swao_in_dummy_riscv>; 66f126890aSEmmanuel Vadot }; 67f126890aSEmmanuel Vadot }; 68f126890aSEmmanuel Vadot }; 69f126890aSEmmanuel Vadot }; 70f126890aSEmmanuel Vadot 71f126890aSEmmanuel Vadot... 72