clk: qcom: support for duplicate freq in RCG2 freq table
Currently RCG code looks up the frequency table during set rate and return the first available frequency greater than requested rate. If CLK_SET_RATE_PARENT flag is set then the set_rate request will go to its parent otherwise the clock framework will configure pre-div, m and n according to the returned frequency table entry. In this case, it is assuming that parent clock will run in the same frequency with which pre-div, m and n has been derived. But it may be possible that the parent clock supports multiple frequency and the same frequency can be derived with different pre-div, m and n values depending upon current frequency. Also, the same frequency can be derived from different parent sources and currently there is no option for having duplicate frequencies in frequency table and choosing the best one according to current rate. Now this patch adds the support for having duplicate frequencies in frequency table. During set rate, it will compare the actual rate for each entry with requested rate and will select the best entry in which the difference will be less. The existing functionality won’t be affected with this code change since this code change will hit only if frequency table has duplicate values. Change-Id: I97d9e1b55d8f3ee095f6f01729af527ba90e50e5 Signed-off-by:Abhishek Sahu <absahu@codeaurora.org> (cherry picked from commit 775e7d3b) Signed-off-by:
Praveenkumar I <ipkumar@codeaurora.org> Change-Id: If10193fc79a3c1375ab73597813745ff1f4df0ad
Please register or sign in to comment