From: Marek Vasut <marex@denx.de>
To: Devin Heitmueller <dheitmueller@kernellabs.com>,
Matt Ranostay <matt@ranostay.consulting>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Attila Kinali <attila@kinali.ch>
Subject: Re: [RFC] v4l2 support for thermopile devices
Date: Fri, 28 Oct 2016 22:40:44 +0200 [thread overview]
Message-ID: <00f453e4-4a58-f01f-c68e-80c88554c3c1@denx.de> (raw)
In-Reply-To: <CAGoCfiw0YJ-iPYG+ZZvdf=5Vh_7wCbB7oO61HU9T3z51kjORiw@mail.gmail.com>
On 10/28/2016 10:30 PM, Devin Heitmueller wrote:
> Hi Matt,
>
>> Need some input for the video pixel data types, which the device we
>> are using (see datasheet links below) is outputting pixel data in
>> little endian 16-bit of which a 12-bits signed value is used. Does it
>> make sense to do some basic processing on the data since greyscale is
>> going to look weird with temperatures under 0C degrees? Namely a cold
>> object is going to be brighter than the hottest object it could read.
>> Or should a new V4L2_PIX_FMT_* be defined and processing done in
>> software? Another issue is how to report the scaling value of 0.25 C
>> for each LSB of the pixels to the respecting recording application.
>
> Regarding the format for the pixel data: I did some research into
> this when doing some driver work for the Seek Thermal (a product
> similar to the FLIR Lepton). While it would be nice to be able to use
> an existing application like VLC or gStreamer to just take the video
> and capture from the V4L2 interface with no additional userland code,
> the reality is that how you colorize the data is going to be highly
> user specific (e.g. what thermal ranges to show with what colors,
> etc). If your goal is really to do a V4L2 driver which returns the
> raw data, then you're probably best returning it in the native
> greyscale format (whether that be an existing V4L2 PIX_FMT or a new
> one needs to be defined), and then in software you can figure out how
> to colorize it.
All true, I also did my share of poking into SEEK Thermal USB and it is
an excellent candidate for a V4L2 driver, that one. But I think this
device here is producing much smaller images, something like 8x8 pixels.
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2016-10-28 20:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 20:14 Matt Ranostay
2016-10-28 20:30 ` Devin Heitmueller
2016-10-28 20:40 ` Marek Vasut [this message]
2016-10-29 2:56 ` Matt Ranostay
2016-10-29 2:58 ` Matt Ranostay
2016-10-28 21:53 ` Hans Verkuil
2016-10-29 2:59 ` Matt Ranostay
2016-11-03 6:10 ` Matt Ranostay
2016-11-03 7:35 ` Antonio Ospite
2016-11-03 8:41 ` Hans Verkuil
2016-11-03 13:21 ` Attila Kinali
2016-11-03 15:11 ` Luca Barbato
2016-11-04 5:11 ` Matt Ranostay
2016-11-17 17:31 ` Sakari Ailus
2016-11-26 13:16 ` Pavel Machek
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=00f453e4-4a58-f01f-c68e-80c88554c3c1@denx.de \
--to=marex@denx.de \
--cc=attila@kinali.ch \
--cc=dheitmueller@kernellabs.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=matt@ranostay.consulting \
/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
all inboxes | Powered by JetHome®