From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: hverkuil <hverkuil@xs4all.nl>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Aviv Greenberg <avivgr@gmail.com>,
linux-media-owner@vger.kernel.org
Subject: Re: per-frame camera metadata (again)
Date: Thu, 24 Dec 2015 19:33:47 +0200 [thread overview]
Message-ID: <1635284.ayChAxBmkc@avalon> (raw)
In-Reply-To: <86a64428cff3a4056742bb169de13e70@xs4all.nl>
Hi Hans,
On Thursday 24 December 2015 13:54:11 hverkuil wrote:
> On 2015-12-24 12:29, Laurent Pinchart wrote:
> >> Control classes are not deprecated, only the use of the control_class
> >> field in struct v4l2_ext_controls to limit the controls in the list to
> >> a single control class is deprecated. That old limitation was from pre-
> >> control-framework times to simplify driver design. With the creation
> >> of the control framework that limitation is no longer needed.
> >
> > Doesn't that effectively deprecated control classes ? We can certainly
> > group controls in categories for documentation purposes, but the control
> > class as an API concept is quite useless nowadays.
>
> No it's not. It is meant to be used by GUIs to group controls into tab
> pages or something similar. See qv4l2 or v4l2-ctl. It's very useful.
I guess I'll just keep disagreeing with you regarding whether the kernel
should provide GUI hints then (cf. V4L2_CTRL_FLAG_SLIDER) :-)
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2015-12-24 17:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 9:37 per-frame camera metadata (again) Guennadi Liakhovetski
2015-12-16 10:02 ` Hans Verkuil
2015-12-16 11:25 ` Guennadi Liakhovetski
2015-12-21 3:41 ` Laurent Pinchart
2015-12-22 11:16 ` Guennadi Liakhovetski
2015-12-22 13:30 ` karthik poduval
2015-12-24 10:54 ` Laurent Pinchart
2015-12-23 17:40 ` Laurent Pinchart
2015-12-24 10:42 ` Guennadi Liakhovetski
2015-12-26 23:47 ` Laurent Pinchart
2016-01-01 15:43 ` Guennadi Liakhovetski
2016-01-05 11:31 ` Guennadi Liakhovetski
2016-01-25 11:14 ` Guennadi Liakhovetski
2016-01-25 19:53 ` Laurent Pinchart
2016-01-26 12:49 ` Guennadi Liakhovetski
2016-01-29 10:08 ` Guennadi Liakhovetski
2015-12-19 0:06 ` Sakari Ailus
2015-12-23 9:47 ` Guennadi Liakhovetski
2015-12-24 10:46 ` Laurent Pinchart
2015-12-24 11:17 ` hverkuil
2015-12-24 11:29 ` Laurent Pinchart
2015-12-24 12:54 ` hverkuil
2015-12-24 17:33 ` Laurent Pinchart [this message]
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=1635284.ayChAxBmkc@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=avivgr@gmail.com \
--cc=g.liakhovetski@gmx.de \
--cc=hverkuil@xs4all.nl \
--cc=linux-media-owner@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=sakari.ailus@linux.intel.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;
as well as URLs for NNTP newsgroup(s).