Re: [PATCH RFC 1/6] dt-bindings: soc: qcom: add QDCP provider

From: Krzysztof Kozlowski

Date: Thu Nov 19 2026 - 09:00:33 EST


On 19/11/2026 10:01, Jie Gan wrote:
> Document the Qualcomm Debug Control Protocol (QDCP) firmware provider
> node used by CoreSight debug and trace blocks that are owned by the
> Qualcomm Embedded Co-Processor (QECP), a separate on-die processor that
> runs its own firmware. QDCP is the QMI (Qualcomm MSM Interface) service,
> carried over QRTR (Qualcomm IPC Router), that Linux uses to ask QECP
> firmware to control those blocks.
>
> The provider is a Qualcomm platform/QMI service node, not a CoreSight
> graph device. It exposes the qcom,qdcp compatible along with
> per-connection QMI service/instance identifiers; the QMI service
> version is the only optional identifier, defaulting to 1.
>
> Signed-off-by: Jie Gan <jie.gan@xxxxxxxxxxxxxxxx>
> ---
> .../devicetree/bindings/soc/qcom/qcom,qdcp.yaml | 81 ++++++++++++++++++++++
> 1 file changed, 81 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/soc/qcom/qcom,qdcp.yaml b/Documentation/devicetree/bindings/soc/qcom/qcom,qdcp.yaml
> new file mode 100644
> index 000000000000..ee0a66b12dde
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/soc/qcom/qcom,qdcp.yaml
> @@ -0,0 +1,81 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/soc/qcom/qcom,qdcp.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Qualcomm Debug Control Protocol (QDCP) provider
> +
> +maintainers:
> + - Jie Gan <jie.gan@xxxxxxxxxxxxxxxx>
> +
> +description: |
> + QDCP is a QMI-based firmware provider used to control CoreSight trace
> + blocks that are owned by the Qualcomm Embedded Co-Processor (QECP) rather
> + than the application processor (AP). CoreSight-facing consumers look up
> + the provider through a "qcom,qdcp" phandle, naming a specific
> + "connection-N" child node rather than the top-level provider node, and
> + issue typed firmware requests instead of programming registers directly.
> +
> + This node does not represent a CoreSight graph device. It is a platform
> + driver that establishes the QMI connections used by consumer drivers such
> + as the Qualcomm QDCP STM source and QDCP-backed TMC/ETR sink.
> +
> + QECP exposes more than one independent QMI service (for example, a
> + separate service used by remote ETM/diag sources). Each QMI connection is
> + described as a child node of the "qcom,qdcp" node rather than as a
> + property of the node itself, so a single provider device can establish
> + more than one connection. A node without any "connection-N" child is valid
> + but provides nothing for consumers to reference.
> +
> +properties:
> + compatible:
> + const: qcom,qdcp

Standard comment - compatibles are not supposed to be generic. That's
why you have entire commit msg to explain any oddities or deviations
from common rules.


No resources here, so this does not look like separate device.

> +
> +patternProperties:
> + "^connection-[0-9]+$":
> + type: object
> + description:
> + A single QMI connection established by the QDCP provider. Consumers
> + reference this child node directly via their "qcom,qdcp" phandle, not
> + the top-level provider node.
> +
> + properties:
> + qcom,service-id:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description:
> + QMI service identifier for this connection.
> +
> + qcom,version:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + default: 1
> + description:
> + QMI service version for this connection.
> +
> + qcom,instance-id:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description:
> + QMI instance identifier for this connection.
> +

Please don't describe firmware contents as random integers in DT.


Best regards,
Krzysztof