Quoting Stephen Boyd (2020-09-16 16:12:01) > The clk_rcg2_dp_determine_rate() function is used for the DP pixel clk. > This function should return the rate that can be achieved by the pixel > clk in 'struct clk_rate_request::rate' and match the logic similar to > what is seen in clk_rcg2_dp_set_rate(). But that isn't the case. Instead > the code merely bubbles the rate request up to the parent of the pixel > clk and doesn't try to do a rational approximation of the rate that > would be achieved by picking some m/n value for the RCG. > > Let's change this logic so that we can assume the parent clk frequency > is fixed (it is because it's the VCO of the DP PLL that is configured > based on the link rate) and so that we can calculate what the m/n value > will be and adjust the req->rate appropriately. > > Cc: Jeykumar Sankaran <jsa...@codeaurora.org> > Cc: Chandan Uddaraju <chand...@codeaurora.org> > Cc: Vara Reddy <va...@codeaurora.org> > Cc: Tanmay Shah <tan...@codeaurora.org> > Cc: Bjorn Andersson <bjorn.anders...@linaro.org> > Cc: Manu Gautam <mgau...@codeaurora.org> > Cc: Sandeep Maheswaram <s...@codeaurora.org> > Cc: Douglas Anderson <diand...@chromium.org> > Cc: Sean Paul <seanp...@chromium.org> > Cc: Stephen Boyd <sb...@kernel.org> > Cc: Jonathan Marek <jonat...@marek.ca> > Cc: Dmitry Baryshkov <dmitry.barysh...@linaro.org> > Cc: Rob Clark <robdcl...@chromium.org> > Signed-off-by: Stephen Boyd <swb...@chromium.org> > ---
Applied to clk-next
