From: Pavel Machek <pavel@denx.de>
To: Matt Ranostay <matt@ranostay.consulting>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Attila Kinali <attila@kinali.ch>, Marek Vasut <marex@denx.de>
Subject: Re: [RFC] v4l2 support for thermopile devices
Date: Sat, 26 Nov 2016 14:16:02 +0100 [thread overview]
Message-ID: <20161126131602.GC20568@xo-6d-61-c0.localdomain> (raw)
In-Reply-To: <CAJ_EiSRM=zn--oFV=7YTE-kipP_ctT2sgSzv64bGrh_MNJbYaQ@mail.gmail.com>
Hi!
> So want to toss a few thoughts on adding support for thermopile
> devices (could be used for FLIR Lepton as well) that output pixel
> data.
> These typically aren't DMA'able devices since they are low speed
> (partly to limiting the functionality to be in compliance with ITAR)
> and data is piped over i2c/spi.
>
> My question is that there doesn't seem to be an other driver that
> polls frames off of a device and pushes it to the video buffer, and
> wanted to be sure that this doesn't currently exist somewhere.
>
> Also more importantly does the mailing list thinks it belongs in v4l2?
> We already came up the opinion on the IIO list that it doesn't belong
> in that subsystem since pushing raw pixel data to a buffer is a bit
> hacky. Also could be generically written with regmap so other devices
> (namely FLIR Lepton) could be easily supported.
>
> 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.
Should we get some kind of flag saying "this is deep infrared"? Most software
won't care, but it would be nice to have enough information so that userspace
can do the right thing automatically...
Thanks,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2016-11-26 13:16 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
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 [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=20161126131602.GC20568@xo-6d-61-c0.localdomain \
--to=pavel@denx.de \
--cc=attila@kinali.ch \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=marex@denx.de \
--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®