xref: /openbmc/linux/Documentation/devicetree/bindings/interconnect/qcom,qdu1000-rpmh.yaml (revision 991f1372)

# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
%YAML 1.2
---
$id: http://devicetree.org/schemas/interconnect/qcom,qdu1000-rpmh.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#

title: Qualcomm RPMh Network-On-Chip Interconnect on QDU1000

maintainers:
  - Georgi Djakov <djakov@kernel.org>
  - Odelu Kukatla <quic_okukatla@quicinc.com>

description: |
   RPMh interconnect providers support system bandwidth requirements through
   RPMh hardware accelerators known as Bus Clock Manager (BCM). The provider is
   able to communicate with the BCM through the Resource State Coordinator (RSC)
   associated with each execution environment. Provider nodes must point to at
   least one RPMh device child node pertaining to their RSC and each provider
   can map to multiple RPMh resources.

properties:
  compatible:
    enum:
      - qcom,qdu1000-clk-virt
      - qcom,qdu1000-gem-noc
      - qcom,qdu1000-mc-virt
      - qcom,qdu1000-system-noc

  '#interconnect-cells': true

  reg:
    maxItems: 1

allOf:
  - $ref: qcom,rpmh-common.yaml#
  - if:
      properties:
        compatible:
          contains:
            enum:
              - qcom,qdu1000-clk-virt
              - qcom,qdu1000-mc-virt
    then:
      properties:
        reg: false
    else:
      required:
        - reg

required:
  - compatible

unevaluatedProperties: false

examples:
  - |
    #include <dt-bindings/interconnect/qcom,qdu1000-rpmh.h>

    system_noc: interconnect@1640000 {
        compatible = "qcom,qdu1000-system-noc";
        reg = <0x1640000 0x45080>;
        #interconnect-cells = <2>;
        qcom,bcm-voters = <&apps_bcm_voter>;
    };

    clk_virt: interconnect-0 {
        compatible = "qcom,qdu1000-clk-virt";
        #interconnect-cells = <2>;
        qcom,bcm-voters = <&apps_bcm_voter>;
    };