From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Sakari Ailus <sakari.ailus@iki.fi>,
Sylwester Nawrocki <snjw23@gmail.com>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
hverkuil@xs4all.nl
Subject: Re: [GIT PATCHES FOR 3.1] s5p-fimc and noon010pc30 driver updates
Date: Tue, 16 Aug 2011 08:07:17 -0700 [thread overview]
Message-ID: <4E4A87A5.9020604@redhat.com> (raw)
In-Reply-To: <201108161059.12300.laurent.pinchart@ideasonboard.com>
Em 16-08-2011 01:59, Laurent Pinchart escreveu:
> Hi Mauro,
>
> On Tuesday 16 August 2011 02:21:09 Mauro Carvalho Chehab wrote:
>> Em 15-08-2011 05:45, Laurent Pinchart escreveu:
>>>> After having it there properly working and tested independently, we may
>>>> consider patches removing V4L2 interfaces that were obsoleted in favor
>>>> of using the libv4l implementation, of course using the Kernel way of
>>>> deprecating interfaces. But doing it before having it, doesn't make any
>>>> sense.
>>>
>>> Once again we're not trying to remove controls, but expose them
>>> differently.
>>
>> See the comments at the patch series, starting from the patches that
>> removes support for S_INPUT. I'm aware that the controls will be exposed
>> by both MC and V4L2 API, althrough having ways to expose/hide controls via
>> V4L2 API makes patch review a way more complicated than it used to be
>> before the MC patches.
>
> The MC API doesn't expose controls. Controls are still exposed by the V4L2 API
> only, but V4L2 can then expose them on subdev nodes in addition to video
> nodes.
To be clear, when I'm talking about MC, I'm meaning also the subdev nodes API,
as a pure V4L2 api application doesn't know anything about them.
Regards,
Mauro
next prev parent reply other threads:[~2011-08-16 15:07 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 [this message]
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
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=4E4A87A5.9020604@redhat.com \
--to=mchehab@redhat.com \
--cc=hverkuil@xs4all.nl \
--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 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.