All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@iki.fi>
To: martin@neutronstar.dyndns.org
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Marek Vasut <marek.vasut@gmail.com>,
	Hans Verkuil <hverkuil@xs4all.nl>,
	linux-media@vger.kernel.org
Subject: Re: [PATCH v3] v4l: Add driver for Micron MT9M032 camera sensor
Date: Thu, 15 Dec 2011 00:11:13 +0200	[thread overview]
Message-ID: <20111214221113.GB3677@valkosipuli.localdomain> (raw)
In-Reply-To: <1323889126.283763.19222@localhost>

Hi Martin,

On Wed, Dec 14, 2011 at 07:58:45PM +0100, martin@neutronstar.dyndns.org 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@vger.kernel.org/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@iki.fi	jabber/XMPP/Gmail: sailus@retiisi.org.uk

  reply	other threads:[~2011-12-14 22:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-14  1:20 [PATCH v3] v4l: Add driver for Micron MT9M032 camera sensor Martin Hostettler
2011-12-14  1:55 ` Marek Vasut
2011-12-14  7:14   ` martin
2011-12-14 13:49     ` Laurent Pinchart
2011-12-14 18:58       ` martin
2011-12-14 22:11         ` Sakari Ailus [this message]
2011-12-17  9:50           ` martin
2011-12-19 10:47             ` Laurent Pinchart
2011-12-19 21:43             ` Sakari Ailus
2011-12-19 10:43         ` Laurent Pinchart
2011-12-14 21:44   ` Guennadi Liakhovetski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20111214221113.GB3677@valkosipuli.localdomain \
    --to=sakari.ailus@iki.fi \
    --cc=hverkuil@xs4all.nl \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=marek.vasut@gmail.com \
    --cc=martin@neutronstar.dyndns.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.