mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
synced 2026-01-11 17:10:13 +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
82 lines
2.5 KiB
YAML
82 lines
2.5 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-source.yaml#
|
|
$schema: http://devicetree.org/meta-schemas/core.yaml#
|
|
|
|
title: ARM Coresight Dummy source 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 source component is for the specific coresight source
|
|
devices kernel don't have permission to access or configure. For some SOCs,
|
|
there would be Coresight source trace components on sub-processor which
|
|
are connected to AP processor via debug bus. For these devices, a dummy driver
|
|
is needed to register them as Coresight source devices, so that paths can be
|
|
created in the driver. 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 source is to build path in kernel
|
|
side for dummy source 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-source
|
|
|
|
label:
|
|
description:
|
|
Description of a coresight device.
|
|
|
|
arm,static-trace-id:
|
|
description: If dummy source needs static id support, use this to set trace id.
|
|
$ref: /schemas/types.yaml#/definitions/uint32
|
|
minimum: 1
|
|
maximum: 111
|
|
|
|
out-ports:
|
|
$ref: /schemas/graph.yaml#/properties/ports
|
|
|
|
properties:
|
|
port:
|
|
description: Output connection from the source to Coresight
|
|
Trace bus.
|
|
$ref: /schemas/graph.yaml#/properties/port
|
|
|
|
required:
|
|
- compatible
|
|
- out-ports
|
|
|
|
additionalProperties: false
|
|
|
|
examples:
|
|
# Minimum dummy source definition. Dummy source connect to coresight funnel.
|
|
- |
|
|
source {
|
|
compatible = "arm,coresight-dummy-source";
|
|
|
|
out-ports {
|
|
port {
|
|
dummy_riscv_out_funnel_swao: endpoint {
|
|
remote-endpoint = <&funnel_swao_in_dummy_riscv>;
|
|
};
|
|
};
|
|
};
|
|
};
|
|
|
|
...
|