From 2dc593d1e4e806a0fb8ff1e362a323f773cbeef0 Mon Sep 17 00:00:00 2001 From: Veera Vegivada Date: Sat, 18 Jul 2020 15:42:14 +0530 Subject: [PATCH] dt-bindings: interconnect: add interconnect bindings Add interconnect device bindings. These devices can be used to describe any RPMH and NoC based interconnect devices for scshrike. Change-Id: I0db869169f33aa73a9fe4be376136b98215f17c9 --- bindings/interconnect/qcom,scshrike.txt | 31 +++++++++++++++++++++++++ 1 file changed, 31 insertions(+) create mode 100644 bindings/interconnect/qcom,scshrike.txt diff --git a/bindings/interconnect/qcom,scshrike.txt b/bindings/interconnect/qcom,scshrike.txt new file mode 100644 index 000000000000..8ab12b107d8c --- /dev/null +++ b/bindings/interconnect/qcom,scshrike.txt @@ -0,0 +1,31 @@ +Qualcomm Technologies, Inc. SCSHRIKE Network-On-Chip interconnect driver binding +------------------------------------------------------------------------------ + +SCSHRIKE 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. + +Required properties : +- compatible : shall contain only one of the following: + "qcom,scshrike-aggre1_noc"; + "qcom,scshrike-aggre2_noc"; + "qcom,scshrike-camnoc_virt"; + "qcom,scshrike-compute_noc"; + "qcom,scshrike-config_noc"; + "qcom,scshrike-dc_noc"; + "qcom,scshrike-gem_noc"; + "qcom,scshrike-ipa_virt"; + "qcom,scshrike-mc_virt"; + "qcom,scshrike-mmss_noc"; + "qcom,scshrike-system_noc"; +- #interconnect-cells : should contain 1 + +Examples: + +aggre1_noc: interconnect@16e0000 { + "qcom,scshrike-aggre1_noc"; + interconnect-cells = <1>; +};