From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Daiane Angolini <daiane.list@gmail.com>,
Jacob Pedersen <jp@circleconsult.dk>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: OV5640 MIPI-CSI2 driver - why the limitations?
Date: Tue, 16 Sep 2014 07:00:09 -0700 [thread overview]
Message-ID: <54184269.2000701@boundarydevices.com> (raw)
In-Reply-To: <CA+jg_OWLcOLaGu82kVsJ-zxNp3p695mdWKpqxqnmBxaeRDc0uA@mail.gmail.com>
On 09/16/2014 06:43 AM, Daiane Angolini wrote:
> On Tue, Sep 16, 2014 at 10:25 AM, Jacob Pedersen <jp@circleconsult.dk> wrote:
>> Hi folks,
>>
>>
>>
>> I'm using a OmniVision OV5640 MIPI-CSI2 image sensor with a iMX6 Quad board,
>> and I'm doing some computer vision applications. I'm curious to know why the
>> driver for the OV5640 sensor is limited to 30 fps, even though the sensor
>> can do 60 fps at 720p and 90 fps at VGA? As far as I can see in the driver,
>> the frame rate is clamped to maximum 30 fps.
>>
>>
>>
>> Is there a technical reason, or is it just because it hasn't been updated
>> for all the supported modes?
>>
>>
>>
>> The driver also limits the available image formats, which makes one required
>> to do the conversion in software or (as in my case) using the IPU. The IPU
>> is fairly fast to do the simple UYVY to RGB24 conversion, but still slower
>> than just getting an RGB image from the sensor.
>
> This limitation is due to the camera device driver. Only few
> configurations are implemented.
>
Those I2C blobs are pretty difficult to get right!
Regards,
Eric
next prev parent reply other threads:[~2014-09-16 14:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 13:25 OV5640 MIPI-CSI2 driver - why the limitations? Jacob Pedersen
2014-09-16 13:43 ` Daiane Angolini
2014-09-16 14:00 ` Eric Nelson [this message]
2014-09-16 14:04 ` Jacob Pedersen
2014-09-16 14:04 ` Daiane Angolini
2014-09-17 12:24 ` Jacob Pedersen
2014-09-17 22:23 ` Alfonso Tamés
2014-09-18 8:06 ` Eric Bénard
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=54184269.2000701@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--cc=daiane.list@gmail.com \
--cc=jp@circleconsult.dk \
--cc=meta-freescale@yoctoproject.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.