All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Longerbeam <slongerbeam@gmail.com>
To: Hans Verkuil <hverkuil@xs4all.nl>,
	Samuel Bobrowicz <sam@elite-embedded.com>,
	linux-media@vger.kernel.org
Subject: Re: OV5640 with 12MHz xclk
Date: Mon, 16 Apr 2018 11:44:20 -0700	[thread overview]
Message-ID: <9b255c35-f163-7db9-a7a8-88c1ac2ceeb1@gmail.com> (raw)
In-Reply-To: <4d87c28b-4adb-86d6-986b-e1ffdceb3138@xs4all.nl>

Hi Sam,

On 04/16/2018 05:26 AM, Hans Verkuil wrote:
> On 04/16/2018 03:39 AM, Samuel Bobrowicz wrote:
>> Can anyone verify if the OV5640 driver works with input clocks other
>> than the typical 24MHz? The driver suggests anything from 6MHz-24MHz
>> is acceptable, but I am running into issues while bringing up a module
>> that uses a 12MHz oscillator. I'd expect that different xclk's would
>> necessitate different register settings for the various resolutions
>> (PLL settings, PCLK width, etc.), however the driver does not seem to
>> modify nearly enough based on the frequency of xclk.
>>
>> Sam
>>
> I'm pretty sure it has never been tested with 12 MHz. The i.MX SabreLite
> seems to use 22 MHz, and I can't tell from the code what the SabreSD uses
> (probably 22 or 24 MHz). Steve will probably know.

On i.MX6, the sabrelite uses the PWM3 clock at 22MHz for the OV5640 xclk.
The SabreSD uses the i.MX6 CKO clock, which is default sourced from the
24 MHz oscillator.

I wouldn't be surprised that there are issues with a 12MHz xclk in the
ov5640 driver. There's probably some assumptions made about the
xclk range in the hardcoded values in those huge register tables. Sorry
I don't have the time to look into it more.

Steve

  reply	other threads:[~2018-04-16 18:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-16  1:39 OV5640 with 12MHz xclk Samuel Bobrowicz
2018-04-16 12:26 ` Hans Verkuil
2018-04-16 18:44   ` Steve Longerbeam [this message]
2018-04-16 23:03     ` Samuel Bobrowicz
2018-04-16 13:04 ` Philipp Zabel

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=9b255c35-f163-7db9-a7a8-88c1ac2ceeb1@gmail.com \
    --to=slongerbeam@gmail.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=sam@elite-embedded.com \
    /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.