[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <54C27AE4.4020702@butterbrot.org>
Date: Fri, 23 Jan 2015 17:46:28 +0100
From: Florian Echtler <floe@...terbrot.org>
To: "Baluta, Teodora" <teodora.baluta@...el.com>,
Sylwester Nawrocki <s.nawrocki@...sung.com>,
Jonathan Cameron <jic23@...nel.org>
CC: Mauro Carvalho Chehab <m.chehab@...sung.com>,
Lars-Peter Clausen <lars@...afoo.de>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-iio <linux-iio@...r.kernel.org>,
LMML <linux-media@...r.kernel.org>,
Hans Verkuil <hverkuil@...all.nl>
Subject: Re: [RFC PATCH 0/3] Introduce IIO interface for fingerprint sensors
Hello Teodora,
On 23.01.2015 14:05, Baluta, Teodora wrote:
> The fingerprint sensor acts more like a scanner device, so the
> closest type is the V4L2_CAP_VIDEO_CAPTURE. However, this is not a
> perfect match because the driver only sends an image, once, when
> triggered. Would it be a better alternative to define a new
> capability type? Or it would be acceptable to simply have a video
> device with no frame buffer or frame rate and the user space
> application to read from the character device /dev/videoX?
Sorry if I jump in here right in the middle of this discussion, but some
time ago, I wrote a fingerprint sensor driver for the Siemens ID Mouse
(still part of the kernel AFAICT) which acts as a misc device and just
creates a character device node that can be used to directly read a PGM
file.
Maybe this would be a slightly simpler approach than pulling in all the
streaming-optimized features of V4L2?
Best, Florian
--
SENT FROM MY DEC VT50 TERMINAL
Download attachment "signature.asc" of type "application/pgp-signature" (182 bytes)
Powered by blists - more mailing lists