A-Team_Digital_Solutions/android_kernel_motorola_sm6375
Watch
2
0
Fork
You've already forked android_kernel_motorola_sm6375
 0
mirror of https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git synced 2026-10-11 07:03:09 -04:00
Code Issues Projects Releases Packages Wiki Activity

dt-bindings: interconnect: add interconnect bindings for direwolf

Browse source 
Add interconnect device bindings. These devices can be used to
describe any RPMH and NoC based interconnect devices for direwolf.

Change-Id: I33cb88c0a34f51277ddb9eec5ff26da4a487b516
This commit is contained in:
Veera Vegivada 2020-09-17 10:43:57 +05:30
commit 3b5ded26dd
1 changed files with 31 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

31
bindings/interconnect/qcom,direwolf.txt Normal file
View file

@ -0,0 +1,31 @@
Qualcomm Technologies, Inc. Direwolf Network-On-Chip interconnect driver binding
------------------------------------------------------------------------------
Direwolf 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,direwolf-aggre1_noc";
"qcom,direwolf-aggre2_noc";
"qcom,direwolf-clk_virt";
"qcom,direwolf-config_noc";
"qcom,direwolf-dc_noc";
"qcom,direwolf-gem_noc";
"qcom,direwolf-lpass_ag_noc";
"qcom,direwolf-mc_virt";
"qcom,direwolf-mmss_noc";
"qcom,direwolf-nspa_noc";
"qcom,direwolf-nspb_noc";
"qcom,direwolf-system_noc_main";
- #interconnect-cells : should contain 1
Examples:
aggre1_noc: interconnect@16c0000 {
"qcom,direwolf-aggre1_noc";
interconnect-cells = <1>;
};