[PATCH v2 06/15] dt-bindings: interconnect: Add Qualcomm Kuno NoC

[Krzysztof Kozlowski]

On Fri, Aug 14, 2026 at 01:01:37PM +0530, Hardeep Sharma wrote:
> Document the RPMh-based Network-on-Chip interconnect providers and
> associated node-ID definitions for the Qualcomm Kuno SoC.
> 
> Signed-off-by: Hardeep Sharma <hardeep.sharma at oss.qualcomm.com>
> ---
>  .../bindings/interconnect/qcom,kuno-rpmh.yaml      | 82 ++++++++++++++++++++
>  include/dt-bindings/interconnect/qcom,kuno.h       | 89 ++++++++++++++++++++++
>  2 files changed, 171 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/interconnect/qcom,kuno-rpmh.yaml b/Documentation/devicetree/bindings/interconnect/qcom,kuno-rpmh.yaml
> new file mode 100644
> index 000000000000..ffbf14356f12
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/interconnect/qcom,kuno-rpmh.yaml
> @@ -0,0 +1,82 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/interconnect/qcom,kuno-rpmh.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Qualcomm RPMh Network-On-Chip Interconnect on Kuno SoC
> +
> +maintainers:
> +  - Hardeep Sharma <hardeep.sharma at oss.qualcomm.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.
> +
> +  See also: include/dt-bindings/interconnect/qcom,kuno.h
> +
> +properties:
> +  compatible:
> +    enum:
> +      - qcom,kuno-aggre-noc
> +      - qcom,kuno-clk-virt
> +      - qcom,kuno-cnoc-main
> +      - qcom,kuno-dc-noc
> +      - qcom,kuno-mc-virt
> +      - qcom,kuno-mem-noc
> +      - qcom,kuno-pcie-anoc
> +      - qcom,kuno-system-noc
> +
> +  reg:
> +    maxItems: 1
> +
> +  clocks:
> +    minItems: 1
> +    maxItems: 4
> +
> +  clock-names:
> +    minItems: 1
> +    maxItems: 4

Why are these flexible?

Look at other bindings how this is done.

Best regards,
Krzysztof