summaryrefslogtreecommitdiff
path: root/include/dt-bindings/interconnect/qcom,qcm2290.h
diff options
context:
space:
mode:
authorShawn Guo <shawn.guo@linaro.org>2021-12-15 03:23:22 +0300
committerGeorgi Djakov <djakov@kernel.org>2021-12-15 08:12:56 +0300
commite39bf2972c6e82eb7c51a78ca990d839aafeb124 (patch)
tree5ca0783925b2aaa6c6dc3890f376a37d972df53a /include/dt-bindings/interconnect/qcom,qcm2290.h
parent08c590409f303d61461b8fcaa9083438e4300448 (diff)
downloadlinux-e39bf2972c6e82eb7c51a78ca990d839aafeb124.tar.xz
interconnect: icc-rpm: Support child NoC device probe
As shown in downstream DT[1], the System NoC of QCM2290 is modelled using 4 fab/noc devices: sys_noc + qup_virt + mmnrt_virt + mmrt_virt. Among those 3 virtual devices, qup is owned by RPM and has no regmap resource, while mmnrt and mmrt are owned by AP and share the same regmap as sys_noc. So it's logical to represent these virtual devices as child nodes of sys_noc in DT, so that such configuration can be supported with a couple of changes on qnoc_probe(): - If there are child nodes, populate them. - If the device descriptor has .regmap_cfg but there is no IOMEM resource for the device, use parent's regmap. [1] https://android.googlesource.com/kernel/msm-extra/devicetree/+/refs/tags/android-11.0.0_r0.56/qcom/scuba-bus.dtsi Signed-off-by: Shawn Guo <shawn.guo@linaro.org> Link: https://lore.kernel.org/r/20211215002324.1727-4-shawn.guo@linaro.org Signed-off-by: Georgi Djakov <djakov@kernel.org>
Diffstat (limited to 'include/dt-bindings/interconnect/qcom,qcm2290.h')
0 files changed, 0 insertions, 0 deletions