From: Sylwester Nawrocki <snjw23@gmail.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Sylwester Nawrocki <s.nawrocki@samsung.com>,
linux-media@vger.kernel.org, laurent.pinchart@ideasonboard.com,
sakari.ailus@iki.fi, g.liakhovetski@gmx.de, hdegoede@redhat.com,
moinejf@free.fr, m.szyprowski@samsung.com,
riverful.kim@samsung.com, sw0312.kim@samsung.com,
Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [PATCH/RFC v3 14/14] vivi: Add controls
Date: Tue, 01 May 2012 20:27:56 +0200 [thread overview]
Message-ID: <4FA02B2C.1020407@gmail.com> (raw)
In-Reply-To: <201205011948.53191.hverkuil@xs4all.nl>
On 05/01/2012 07:48 PM, Hans Verkuil wrote:
> On Tue May 1 2012 19:40:55 Sylwester Nawrocki wrote:
>> On 04/30/2012 06:09 PM, Hans Verkuil wrote:
>>> On Friday 27 April 2012 16:23:31 Sylwester Nawrocki wrote:
...
>>> Why add these controls to vivi? It doesn't belong here.
>>
>> Yeah, my intention was to provide some basic means for validating the
>> new controls, especially integer menu ones. I really don't use vivi
>> for testing, but I think not many people have currently access to the
>> hardware I work with. So this is just in case Mauro wants to do tests
>> of the core control framework changes. I agree this patch doesn't
>> make sense for anything other than that.
>>
>> I have also a small patch for v4l2-ctl to support integer menu
>> control enumeration. However I run into some weird problems when
>> I cross compiled it for ARM (individual menu names are not listed)
>> and didn't get around to fix that yet. So I didn't yet send that
>> v4l2-ctl patch out.
>
> There is already an int-menu control in vivi, and v4l2-ctl already
> support integer menus as well (as does qv4l2 and v4l2-compliance).
>
> So this should be all ready for you.
Oh, it is there already! Must have been too busy to notice that :/
> BTW, it would be nice to get g/s_selection support in v4l2-ctl, that is
> still missing. And a good test in v4l2-compliance would be great as well.
Yeah, I noticed that too recently, we use selections on video nodes
in some drivers and media-ctl can be only used for subdevs. I'll try
to find some time to add selection ioctls support to v4l2-ctl first,
perhaps this weekend.
> Have you run v4l2-compliance lately? It's getting pretty good at
> catching all sorts of inconsistencies.
No, I haven't used it for a while. I know from the last run I need to
add G/S_PRIORITY support in one of the drivers. :)
I'm going to give it a try, however I'm going to need to deal with
more and more media controller nodes. For example the fimc-lite
camera host driver I posted recently can be used with media controller
API only, I set only V4L2_CAP_STREAMING at the video node, as it was
agreed previously. I assume some support for media controller API
needs to be added to v4l2-compliance as well ?
--
Regards,
Sylwester
next prev parent reply other threads:[~2012-05-01 18:27 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 14:23 [PATCH/RFC v3 00/14] V4L camera control enhancements Sylwester Nawrocki
2012-04-27 14:23 ` [PATCH/RFC v3 01/14] V4L: Add helper function for standard integer menu controls Sylwester Nawrocki
2012-04-30 15:20 ` Hans Verkuil
2012-04-30 15:37 ` Sylwester Nawrocki
2012-04-27 14:23 ` [PATCH/RFC v3 02/14] V4L: Add camera exposure bias control Sylwester Nawrocki
2012-04-27 14:23 ` [PATCH/RFC v3 03/14] V4L: Add an extended camera white balance control Sylwester Nawrocki
2012-04-27 14:30 ` Hans de Goede
2012-04-27 14:23 ` [PATCH/RFC v3 04/14] V4L: Add camera wide dynamic range control Sylwester Nawrocki
2012-04-30 15:50 ` Hans Verkuil
2012-04-30 15:54 ` Hans Verkuil
2012-05-01 17:33 ` Sylwester Nawrocki
2012-04-27 14:23 ` [PATCH/RFC v3 05/14] V4L: Add camera image stabilization control Sylwester Nawrocki
2012-04-27 14:23 ` [PATCH/RFC v3 06/14] V4L: Add camera ISO sensitivity controls Sylwester Nawrocki
2012-04-27 14:23 ` [PATCH/RFC v3 07/14] V4L: Add camera exposure metering control Sylwester Nawrocki
2012-04-27 14:23 ` [PATCH/RFC v3 08/14] V4L: Add camera scene mode control Sylwester Nawrocki
2012-04-27 14:23 ` [PATCH/RFC v3 09/14] V4L: Add camera 3A lock control Sylwester Nawrocki
2012-04-30 15:59 ` Hans Verkuil
2012-05-01 17:38 ` Sylwester Nawrocki
2012-04-27 14:23 ` [PATCH/RFC v3 10/14] V4L: Add auto focus targets to the selections API Sylwester Nawrocki
2012-04-27 14:23 ` [PATCH/RFC v3 11/14] V4L: Add auto focus targets to the subdev " Sylwester Nawrocki
2012-04-27 14:23 ` [PATCH/RFC v3 12/14] V4L: Add camera auto focus controls Sylwester Nawrocki
2012-04-27 14:23 ` [PATCH/RFC v3 13/14] V4L: Add S5C73M3 sensor sub-device driver Sylwester Nawrocki
2012-04-27 14:23 ` [PATCH/RFC v3 14/14] vivi: Add controls Sylwester Nawrocki
2012-04-30 16:09 ` Hans Verkuil
2012-05-01 17:40 ` Sylwester Nawrocki
2012-05-01 17:48 ` Hans Verkuil
2012-05-01 18:27 ` Sylwester Nawrocki [this message]
2012-05-01 19:02 ` Hans Verkuil
2012-04-30 15:10 ` [PATCH/RFC v3 00/14] V4L camera control enhancements Sylwester Nawrocki
2012-04-30 16:11 ` Hans Verkuil
2012-05-01 17:58 ` Sylwester Nawrocki
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=4FA02B2C.1020407@gmail.com \
--to=snjw23@gmail.com \
--cc=g.liakhovetski@gmx.de \
--cc=hdegoede@redhat.com \
--cc=hverkuil@xs4all.nl \
--cc=kyungmin.park@samsung.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=moinejf@free.fr \
--cc=riverful.kim@samsung.com \
--cc=s.nawrocki@samsung.com \
--cc=sakari.ailus@iki.fi \
--cc=sw0312.kim@samsung.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.