From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Nicolas Dufresne <nicolas@ndufresne.ca>
Cc: Pavel Machek <pavel@ucw.cz>,
linux-media@vger.kernel.org, sakari.ailus@linux.intel.com,
niklas.soderlund@ragnatech.se, jerry.w.hu@intel.com,
mario.limonciello@dell.com
Subject: Re: Software-only image processing for Intel "complex" cameras
Date: Fri, 22 Jun 2018 03:36:40 +0900 [thread overview]
Message-ID: <20180622033640.298f6ee1@vela.lan> (raw)
In-Reply-To: <b7707ec241d9d2d2966bdc32f7bb9bc55ac55c5d.camel@ndufresne.ca>
Em Wed, 20 Jun 2018 16:57:59 -0400
Nicolas Dufresne <nicolas@ndufresne.ca> escreveu:
> The IPU3 sensor produce a vendor specific form of bayer. If we manage
> to implement support for this format, it would likely be done in
> software. I don't think anyone can answer your other questions has no
> one have ever implemented this, hence measure performance.
Decoding that bayer-like specific format is something that we currently
do at libv4lconvert. IMHO, we should have support for it inside the
library, even if the device is capable of decoding it via a mem2mem
device. If not for usage in "production", being able to read it from
the sensor directly helps to test it. It might also be used on some
applications where there would be no need for 3A algorithms to run
(for example, on industrial cameras where the light and the distance of
the objects don't change).
Cheers,
Mauro
next prev parent reply other threads:[~2018-06-21 18:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 20:38 Software-only image processing for Intel "complex" cameras Pavel Machek
2018-06-20 20:57 ` Nicolas Dufresne
2018-06-20 21:11 ` Pavel Machek
2018-06-21 13:41 ` Mario.Limonciello
2018-06-21 18:49 ` Mauro Carvalho Chehab
2018-06-21 18:58 ` Mario.Limonciello
2018-06-21 21:08 ` Mauro Carvalho Chehab
2018-06-21 21:40 ` Mauro Carvalho Chehab
2018-06-25 9:48 ` Zheng, Jian Xu
2018-06-25 13:10 ` Mauro Carvalho Chehab
2018-07-27 10:58 ` Javier Martinez Canillas
2018-06-23 21:29 ` Pavel Machek
2018-06-21 18:36 ` Mauro Carvalho Chehab [this message]
2018-06-29 6:02 ` Tomasz Figa
2018-06-29 9:18 ` Pavel Machek
2018-06-29 9:28 ` Tomasz Figa
2018-06-29 10:52 ` 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=20180622033640.298f6ee1@vela.lan \
--to=mchehab+samsung@kernel.org \
--cc=jerry.w.hu@intel.com \
--cc=linux-media@vger.kernel.org \
--cc=mario.limonciello@dell.com \
--cc=nicolas@ndufresne.ca \
--cc=niklas.soderlund@ragnatech.se \
--cc=pavel@ucw.cz \
--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