From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: "Ivan T. Ivanov" <iivanov@mm-sol.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Sylwester Nawrocki <snjw23@gmail.com>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
Sakari Ailus <sakari.ailus@iki.fi>,
Hans de Goede <hdegoede@redhat.com>
Subject: Re: [GIT PATCHES FOR 3.1] s5p-fimc and noon010pc30 driver updates
Date: Wed, 17 Aug 2011 06:27:58 -0700 [thread overview]
Message-ID: <4E4BC1DE.1060404@redhat.com> (raw)
In-Reply-To: <1313584678.14286.27.camel@iivanov-desktop>
Em 17-08-2011 05:37, Ivan T. Ivanov escreveu:
>
> Hi everybody,
>
> On Wed, 2011-08-17 at 05:25 -0700, Mauro Carvalho Chehab wrote:
>> Em 17-08-2011 00:57, Laurent Pinchart escreveu:
>>> Hi Mauro,
>>>
>>> On Wednesday 17 August 2011 00:36:44 Mauro Carvalho Chehab wrote:
>>>> Em 16-08-2011 08:44, Laurent Pinchart escreveu:
>>>>> On Tuesday 16 August 2011 17:30:47 Mauro Carvalho Chehab wrote:
>>>>>> Em 16-08-2011 01:57, Laurent Pinchart escreveu:
>>>>> No. S_INPUT shouldn't be use to select between sensors. The hardware
>>>>> pipeline is more complex than just that. We can't make it all fit in the
>>>>> S_INPUT API.
>>>>>
>>>>> For instance, when switching between a b&w and a color sensor you will
>>>>> need to reconfigure the whole pipeline to select the right gamma table,
>>>>> white balance parameters, color conversion matrix, ... That's not
>>>>> something we want to hardcode in the kernel. This needs to be done from
>>>>> userspace.
>>>>
>>>> This is something that, if it is not written somehwere, no userspace
>>>> applications not developed by the hardware vendor will ever work.
>>>>
>>>> I don't see any code for that any at the kernel or at libv4l. Am I missing
>>>> something?
>>>
>>> Code for that needs to be written in libv4l. It's not there yet as I don't
>>> think we have any hardware for this particular example at the moment :-)
>>>
>> As no pure V4L2 application would set the pipelines as you've said, and
>> no libv4l code exists yet,
>
>
> Actually there is such code for OMAP3 ISP driver. Plug-in support in
> libv4l have been extended a little bit [1] and plugin-in which handle
> request for "regular" video device nodes /dev/video0 and /dev/video1
> and translate them to MC and sub-device API have been posted here [2],
> but is still not merged.
>
> Regards,
> iivanov
>
> [1] http://www.spinics.net/lists/linux-media/msg35570.html
> [2] http://www.spinics.net/lists/linux-media/msg32539.html
Ah, ok. So, it is just the usual delay of having some features merged.
Hans G.,
FYI. Please review the OMAP3 MC-aware patches for libv4l when you have
some time for that.
Thanks!
Mauro
next prev parent reply other threads:[~2011-08-17 13:28 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 16:35 [GIT PATCHES FOR 3.1] s5p-fimc and noon010pc30 driver updates Sylwester Nawrocki
2011-07-28 2:55 ` Mauro Carvalho Chehab
2011-07-28 10:09 ` Sylwester Nawrocki
2011-07-28 13:20 ` Mauro Carvalho Chehab
2011-07-28 22:57 ` Sylwester Nawrocki
2011-07-29 4:02 ` Mauro Carvalho Chehab
2011-07-29 8:36 ` Laurent Pinchart
2011-08-09 20:05 ` Mauro Carvalho Chehab
2011-08-09 23:18 ` Sakari Ailus
2011-08-10 0:22 ` Mauro Carvalho Chehab
2011-08-10 8:41 ` Sylwester Nawrocki
2011-08-10 12:52 ` Mauro Carvalho Chehab
2011-08-15 12:45 ` Laurent Pinchart
2011-08-16 0:21 ` Mauro Carvalho Chehab
2011-08-16 8:59 ` Laurent Pinchart
2011-08-16 15:07 ` Mauro Carvalho Chehab
2011-08-15 12:30 ` Laurent Pinchart
2011-08-16 0:13 ` Mauro Carvalho Chehab
2011-08-16 8:57 ` Laurent Pinchart
2011-08-16 15:30 ` Mauro Carvalho Chehab
2011-08-16 15:44 ` Laurent Pinchart
2011-08-16 22:36 ` Mauro Carvalho Chehab
2011-08-17 7:57 ` Laurent Pinchart
2011-08-17 12:25 ` Mauro Carvalho Chehab
2011-08-17 12:37 ` Ivan T. Ivanov
2011-08-17 13:27 ` Mauro Carvalho Chehab [this message]
2011-08-17 12:33 ` Sakari Ailus
2011-08-16 21:47 ` Sylwester Nawrocki
2011-08-17 6:13 ` Embedded device and the V4L2 API support - Was: " Mauro Carvalho Chehab
2011-08-20 11:27 ` Sylwester Nawrocki
2011-08-20 12:12 ` Mauro Carvalho Chehab
2011-08-24 22:29 ` Sakari Ailus
2011-08-25 12:43 ` Mauro Carvalho Chehab
2011-08-26 13:45 ` Laurent Pinchart
2011-08-26 14:16 ` Hans Verkuil
2011-08-26 15:09 ` Mauro Carvalho Chehab
2011-08-26 15:29 ` Hans Verkuil
2011-08-26 17:32 ` Mauro Carvalho Chehab
2011-08-29 9:24 ` Laurent Pinchart
2011-08-29 14:53 ` Mauro Carvalho Chehab
2011-08-29 9:12 ` Laurent Pinchart
2011-08-30 20:34 ` Sakari Ailus
2011-08-03 14:28 ` Sylwester Nawrocki
2011-07-29 8:17 ` 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=4E4BC1DE.1060404@redhat.com \
--to=mchehab@redhat.com \
--cc=hdegoede@redhat.com \
--cc=iivanov@mm-sol.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=sakari.ailus@iki.fi \
--cc=snjw23@gmail.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