On 6/25/25 11:13 AM, Luca Weiss wrote: > Add driver for the Qualcomm interconnect buses found in SM7635 based > platforms. The topology consists of several NoCs that are controlled by > a remote processor that collects the aggregated bandwidth for each > master-slave pairs. > > Signed-off-by: Luca Weiss <luca.we...@fairphone.com> > ---
[...] > +static const struct of_device_id qnoc_of_match[] = { > + { .compatible = "qcom,sm7635-aggre1-noc", > + .data = &sm7635_aggre1_noc}, > + { .compatible = "qcom,sm7635-aggre2-noc", > + .data = &sm7635_aggre2_noc}, > + { .compatible = "qcom,sm7635-clk-virt", > + .data = &sm7635_clk_virt}, > + { .compatible = "qcom,sm7635-cnoc-cfg", > + .data = &sm7635_cnoc_cfg}, > + { .compatible = "qcom,sm7635-cnoc-main", > + .data = &sm7635_cnoc_main}, > + { .compatible = "qcom,sm7635-gem-noc", > + .data = &sm7635_gem_noc}, > + { .compatible = "qcom,sm7635-lpass-ag-noc", > + .data = &sm7635_lpass_ag_noc}, > + { .compatible = "qcom,sm7635-mc-virt", > + .data = &sm7635_mc_virt}, > + { .compatible = "qcom,sm7635-mmss-noc", > + .data = &sm7635_mmss_noc}, > + { .compatible = "qcom,sm7635-nsp-noc", > + .data = &sm7635_nsp_noc}, > + { .compatible = "qcom,sm7635-pcie-anoc", > + .data = &sm7635_pcie_anoc}, > + { .compatible = "qcom,sm7635-system-noc", > + .data = &sm7635_system_noc}, One line per entry, please In addition to what Dmitry asked for, please also look into porting QoS settings - those will require additional clock references in the ICC nodes and as such, the bindings will be altered (which we'd prefer to get right from the getgo). As far as testing goes, there may not be any apparent perf changes, but if you get the clocks list wrong, the device will lock up at boot (unless you're booting with clk_ignore_unused and friends) Konrad