Re: why does aptina_pll_calculate insist on exact division?

2018-08-14 Thread Sakari Ailus
Hi, On Tue, Aug 14, 2018 at 10:30:14AM +0300, Laurent Pinchart wrote: > Hi Helmut, > > (CC'ing Sakari Ailus who is our current PLL expert after spending so much > time > on the SMIA PLL code) > > On Tuesday, 14 August 2018 09:35:40 EEST Helmut Grohne wrote: > > Hi, > > > > I tried using the

Re: why does aptina_pll_calculate insist on exact division?

2018-08-14 Thread Helmut Grohne
Hi, Thank you for the quick and helpful answer. On Tue, Aug 14, 2018 at 09:30:14AM +0200, Laurent Pinchart wrote: > How do you mean ? The only place where pix_clock_max is used is in the > following code: > > if (pll->pix_clock == 0 || pll->pix_clock > limits->pix_clock_max) { >

Re: why does aptina_pll_calculate insist on exact division?

2018-08-14 Thread Laurent Pinchart
Hi Helmut, (CC'ing Sakari Ailus who is our current PLL expert after spending so much time on the SMIA PLL code) On Tuesday, 14 August 2018 09:35:40 EEST Helmut Grohne wrote: > Hi, > > I tried using the aptina_pll_calculate for a "new" imager and ran into > problems. After filling out

why does aptina_pll_calculate insist on exact division?

2018-08-14 Thread Helmut Grohne
Hi, I tried using the aptina_pll_calculate for a "new" imager and ran into problems. After filling out aptina_pll_limits from the data sheet, I was having a hard time finding a valid pix_clock. Most of the ones I tried are rejected by aptina_pll_calculate for various reasons. In particular, no