From: Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>
To: Michael Trimarchi <michael@panicking.kicks-ass.org>
Cc: "Aguirre, Sergio" <saaguirre@ti.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: omap34xxcam question?
Date: Thu, 04 Feb 2010 16:21:23 +0200 [thread overview]
Message-ID: <4B6AD7E3.6020102@maxwell.research.nokia.com> (raw)
In-Reply-To: <4B502982.4050508@panicking.kicks-ass.org>
Hi Michael,
Michael Trimarchi wrote:
> Aguirre, Sergio wrote:
...
>> So, if I got you right, you're saying that, there should be priorities
>> for sensor baseformats, depending on the preference specified
>> somewhere in the boardfile?
>
> Yes, that is the idea. Try to provide a better patch later, I'm working
> hard on the sensor part :)
Apologies for my late answer.
The frame sizes in our sensor drivers are in width descending order. The
selection has been working somehow so far but it's definitely not perfect.
We're converting the ISP driver to use the Media controller so this code
will be dropped in near future probably. In that case the user space has
to select the sensor mode it wants to use as well.
Regular V4L2 applications of course cannot be expected to do that. But
it probably should be handled in user space (i.e. libv4l) or by offering
a dummy video node that just produces some kind of images.
--
Sakari Ailus
sakari.ailus@maxwell.research.nokia.com
next prev parent reply other threads:[~2010-02-04 14:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 12:00 omap34xxcam question? Michael Trimarchi
2010-01-14 17:09 ` Aguirre, Sergio
2010-01-14 17:25 ` Michael Trimarchi
2010-01-14 17:33 ` Aguirre, Sergio
2010-01-14 17:39 ` Michael Trimarchi
2010-01-14 19:08 ` [RFC PATCH] fix try_pix_parm loop Michael Trimarchi
2010-01-14 23:57 ` omap34xxcam question? Aguirre, Sergio
2010-01-15 8:38 ` Michael Trimarchi
2010-01-19 17:30 ` Michael Trimarchi
2010-02-04 14:21 ` Sakari Ailus [this message]
2010-02-04 15:06 ` Michael Trimarchi
2010-02-05 7:43 ` Sakari Ailus
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=4B6AD7E3.6020102@maxwell.research.nokia.com \
--to=sakari.ailus@maxwell.research.nokia.com \
--cc=linux-media@vger.kernel.org \
--cc=michael@panicking.kicks-ass.org \
--cc=saaguirre@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox