From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>
Cc: Sylwester Nawrocki <snjw23@gmail.com>,
Hans Verkuil <hverkuil@xs4all.nl>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
Nayden Kanchev <nkanchev@mm-sol.com>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
David Cohen <dacohen@gmail.com>,
Kim HeungJun <riverful@gmail.com>,
andrew.b.adams@gmail.com, Sung Hee Park <shpark7@stanford.edu>
Subject: Re: [RFC v4] V4L2 API for flash devices
Date: Tue, 07 Jun 2011 09:17:50 -0300 [thread overview]
Message-ID: <4DEE16EE.9030200@redhat.com> (raw)
In-Reply-To: <4DD4D0D2.7030609@maxwell.research.nokia.com>
Em 19-05-2011 05:12, Sakari Ailus escreveu:
> Sylwester Nawrocki wrote:
>>>> These were mostly fixed point arithmetic numbers in [32-bit numerator/
>>>> 32-bit denominator] form carrying exposure time, shutter speed, aperture,
>>>> brightness, flash, etc. information. The tags could be read from ISP after
>>>> it buffered a frame in its memory and processed it.
>>>> In case of a JPEG image format the tags can be embedded into the main
>>>> image file. But the image processors not always supported that so we used
>>>> to have an ioctl for the purpose of retrieving the metadata in user space.
>>>> In some cases it is desired to read data directly from the driver rather
>>>> than parsing a relatively large buffer.
>>>> It would be good to have a uniform interface for passing such data to
>>>> applications. I think in that particular use case a control id/value pair
>>>> sequences would do.
> - Which formats are your rational numbers in? A kernel interface can't
> really have floating point numbers, so there would need to be a sane way
> to pass these to user space.
The V4L2 API has support for rational numbers. The frame rate is specified as a
rational number. There's a struct for that:
struct v4l2_fract {
__u32 numerator;
__u32 denominator;
};
Cheers,
Mauro
next prev parent reply other threads:[~2011-06-07 12:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 18:49 [RFC v4] V4L2 API for flash devices Sakari Ailus
2011-05-07 12:46 ` Hans Verkuil
2011-05-07 17:42 ` Sylwester Nawrocki
2011-05-08 22:11 ` Sakari Ailus
2011-05-10 20:40 ` Sylwester Nawrocki
2011-05-17 20:34 ` Sakari Ailus
2011-05-18 7:10 ` Laurent Pinchart
2011-05-18 7:30 ` Sakari Ailus
2011-05-18 22:21 ` Sylwester Nawrocki
2011-05-19 8:12 ` Sakari Ailus
2011-06-07 12:17 ` Mauro Carvalho Chehab [this message]
2011-05-08 15:48 ` Sakari Ailus
2011-05-14 13:13 ` Andy Walls
2011-05-16 9:23 ` 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=4DEE16EE.9030200@redhat.com \
--to=mchehab@redhat.com \
--cc=andrew.b.adams@gmail.com \
--cc=dacohen@gmail.com \
--cc=g.liakhovetski@gmx.de \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=nkanchev@mm-sol.com \
--cc=riverful@gmail.com \
--cc=sakari.ailus@maxwell.research.nokia.com \
--cc=shpark7@stanford.edu \
--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