Hi, On Wed, Jan 26, 2022 at 6:58 AM Sascha Hauer <s.hauer@xxxxxxxxxxxxxx> wrote: > > From: Douglas Anderson <dianders at chromium.org> > > The previous tables for mpll_cfg and curr_ctrl were created using the > 20-pages of example settings provided by the PHY vendor. Those > example settings weren't particularly dense, so there were places > where we were guessing what the settings would be for 10-bit and > 12-bit (not that we use those anyway). It was also always a lot of > extra work every time we wanted to add a new clock rate since we had > to cross-reference several tables. > > In <http://crosreview.com/285855> I've gone through the work to figure The `crosreview.com` syntax doesn't seem to work anymore. Could maybe update to https://crrev.com/c/285855 ? > out how to generate this table automatically. Let's now use the > automatically generated table and then we'll never need to look at it > again. > > We only support 8-bit mode right now and only support a small number > of clock rates and and I've verified that the only 8-bit rate that was > affected was 148.5. That mode appears to have been wrong in the old > table. > > Changes since v3: > - new patch > > Signed-off-by: Douglas Anderson <dianders at chromium.org> > Signed-off-by: Yakir Yang <ykk at rock-chips.com> Should probably change the "at" to "@" ? > Reviewed-by: Stéphane Marchesin <marcheu at chromium.org> In general shouldn't carry downstream reviews when posting upstream unless you're certain that the person intended it... It's been a long time, but in general I think I was fairly confident in the numbers that my script pumped out, at least given the caveat of no pixel repetition and 8-bit only. That being said, I didn't have any inside knowledge of the hardware and just figured out formulas that seemed to match the table that I had. YMMV. I'll also say that when I did a rebase of veyron (rk3288-based Chromebook) to 4.19 about 2.5 years ago, I ended up squashing several of these patches into 1. That can be found at <https://crrev.com/c/1661056>. That also has details about why some of these patches never made it upstream. The main reason, at least in the case of rk3288, was the PLL sharing problem that nobody ever solved. rk3288 didn't have quite enough PLLs and thus, if you were using both VOPs, one of the VOPs was going to be severely limited in what pixel clocks it could make. There was no framework deciding which VOP should be limited and how the system should react to this... In any case, I'm pretty far disconnected from all this stuff now, but I wish you the best of luck in trying to get it all solved! -Doug
