mirror of
https://github.com/torvalds/linux.git
synced 2025-12-07 20:06:24 +00:00
1ad38ef4db
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 label to show hardware context information of each coresight device. There will be a sysfs node label in each device folder. cat /sys/bus/coresight/devices/cti_sys0/label Signed-off-by: Mao Jinlong <quic_jinlmao@quicinc.com> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Reviewed-by: Mike Leach <mike.leach@linaro.org> Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com> Link: https://lore.kernel.org/r/20250816072529.3716968-2-quic_jinlmao@quicinc.com
78 lines
2.4 KiB
YAML
78 lines
2.4 KiB
YAML
# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
|
|
%YAML 1.2
|
|
---
|
|
$id: http://devicetree.org/schemas/arm/arm,coresight-dummy-sink.yaml#
|
|
$schema: http://devicetree.org/meta-schemas/core.yaml#
|
|
|
|
title: ARM Coresight Dummy sink component
|
|
|
|
description: |
|
|
CoreSight components are compliant with the ARM CoreSight architecture
|
|
specification and can be connected in various topologies to suit a particular
|
|
SoCs tracing needs. These trace components can generally be classified as
|
|
sinks, links and sources. Trace data produced by one or more sources flows
|
|
through the intermediate links connecting the source to the currently selected
|
|
sink.
|
|
|
|
The Coresight dummy sink component is for the specific coresight sink devices
|
|
kernel don't have permission to access or configure, e.g., CoreSight EUD on
|
|
Qualcomm platforms. It is a mini-USB hub implemented to support the USB-based
|
|
debug and trace capabilities. For this device, a dummy driver is needed to
|
|
register it as Coresight sink device in kernel side, so that path can be
|
|
created in the driver. Then the trace flow would be transferred to EUD via
|
|
coresight link of AP processor. It provides Coresight API for operations on
|
|
dummy source devices, such as enabling and disabling them. It also provides
|
|
the Coresight dummy source paths for debugging.
|
|
|
|
The primary use case of the coresight dummy sink is to build path in kernel
|
|
side for dummy sink component.
|
|
|
|
maintainers:
|
|
- Mike Leach <mike.leach@linaro.org>
|
|
- Suzuki K Poulose <suzuki.poulose@arm.com>
|
|
- James Clark <james.clark@linaro.org>
|
|
- Mao Jinlong <quic_jinlmao@quicinc.com>
|
|
- Hao Zhang <quic_hazha@quicinc.com>
|
|
|
|
properties:
|
|
compatible:
|
|
enum:
|
|
- arm,coresight-dummy-sink
|
|
|
|
label:
|
|
description:
|
|
Description of a coresight device.
|
|
|
|
in-ports:
|
|
$ref: /schemas/graph.yaml#/properties/ports
|
|
|
|
properties:
|
|
port:
|
|
description: Input connection from the Coresight Trace bus to
|
|
dummy sink, such as Embedded USB debugger(EUD).
|
|
|
|
$ref: /schemas/graph.yaml#/properties/port
|
|
|
|
required:
|
|
- compatible
|
|
- in-ports
|
|
|
|
additionalProperties: false
|
|
|
|
examples:
|
|
# Minimum dummy sink definition. Dummy sink connect to coresight replicator.
|
|
- |
|
|
sink {
|
|
compatible = "arm,coresight-dummy-sink";
|
|
|
|
in-ports {
|
|
port {
|
|
eud_in_replicator_swao: endpoint {
|
|
remote-endpoint = <&replicator_swao_out_eud>;
|
|
};
|
|
};
|
|
};
|
|
};
|
|
|
|
...
|