Hi Martin,
On Wed, Dec 14, 2011 at 07:58:45PM +0100, martin@xxxxxxxxxxxxxxxxxxxxxx wrote:
...
> > > > > +static int mt9m032_setup_pll(struct mt9m032 *sensor)
> > > > > +{
> > > > > + struct mt9m032_platform_data* pdata = sensor->pdata;
> > > > > + u16 reg_pll1;
> > > > > + unsigned int pre_div;
> > > > > + int res, ret;
> > > > > +
> > > > > + /* TODO: also support other pre-div values */
> >
> > I might already have mentioned this, but wouldn't it be time to work a on real
> > PLL setup code that compute the pre-divisor, multiplier and output divisor
> > dynamically from the input and output clock frequencies ?
>
> I'm not sure what the implications for quality and stability of such a
> generic setup would be. My gut feeling is most users go with known working
> hardcoded values.
You'd get a lot better control of the sensor as a bonus in doing so. Also,
you could program the sensor properly suitable for the host it is connected
to, achieving optimal maximum frame rates for it.
These values tend to be relatively board / bridge dependent. On one board
some frequencies might not be usable even if they do not exceed the maximum
for the bridge.
Please also see this:
<URL:http://www.mail-archive.com/linux-media@xxxxxxxxxxxxxxx/msg39798.html>
> Also in the datasheet i have access to, this is totally underdocumented.
That's unfortunate. Laurent, is yours the same?
--
Sakari Ailus
e-mail: sakari.ailus@xxxxxx jabber/XMPP/Gmail: sailus@xxxxxxxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
