On 02-07-19, 18:10, Saravana Kannan wrote: > Interconnects and interconnect paths quantify their performance levels in > terms of bandwidth and not in terms of frequency. So similar to how we have > frequency based OPP tables in DT and in the OPP framework, we need > bandwidth OPP table support in the OPP framework and in DT. Since there can > be more than one interconnect path used by a device, we also need a way to > assign a bandwidth OPP table to an interconnect path. > > This patch series: > - Adds opp-peak-KBps and opp-avg-KBps properties to OPP DT bindings > - Adds interconnect-opp-table property to interconnect DT bindings > - Adds OPP helper functions for bandwidth OPP tables > - Adds icc_get_opp_table() to get the OPP table for an interconnect path > > So with the DT bindings added in this patch series, the DT for a GPU > that does bandwidth voting from GPU to Cache and GPU to DDR would look > something like this: And what changed since V2 ? -- viresh
