All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil@xs4all.nl>
To: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>,
	linux-media <linux-media@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Subject: Re: RFC: HSV format
Date: Fri, 27 May 2016 10:56:12 +0200	[thread overview]
Message-ID: <57480BAC.6050201@xs4all.nl> (raw)
In-Reply-To: <CAPybu_3+PsND193UKfrP7Hy_Qs7gu=QWRxZcmfiDaDRmiC6h4g@mail.gmail.com>

On 05/24/2016 11:19 PM, Ricardo Ribalda Delgado wrote:
> Hi
> 
> HSV is a  cylindrical-coordinate representation of a color. It is very
> useful for computer vision because the Hue component can be used to
> segment a scene.
> 
> My plan was to add a format in videodev2.h and then add support for
> vivid, libv4l2-convert and qv4l2.
> 
> There are also plans to prepare a patch for opencv to use this format
> without any software conversion, and also for Gstreamer... but all
> these changes depend on the changes on videodev2.h
> 
> The question is how open would be the linux-media community for such a
> change, considering that there is no real device driver using it in
> tree ( Our hardware is currently out of tree_
> 
> Today we only have an HSV format on v4l2-mediabus.h
> V4L2_MBUS_FROM_MEDIA_BUS_FMT(AHSV8888_1X32), but no HSV format on
> videodev2.h

It's always a bit tricky to decide what to do with this. In general I feel
uncomfortable with the idea of defines that aren't used. Certainly for very
hardware-specific formats I don't like the idea of adding unused formats to
the kernel.

In this case I am however inclined to accept it provided:

- it's not a crazy format: e.g. AHSV (32 bit) or HSV (24 bit) would be fine,
  but some weird macroblock format would be a lot more problematic.
- it's fully documented
- implemented in vivid etc.
- patches adding it to opencv/gstreamer are CC-ed to linux-media as well so
  I know that it is going to be used there.

But you will have to check with Mauro as well, he has the final say in this.

Regards,

	Hans

      reply	other threads:[~2016-05-27  8:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-24 21:19 RFC: HSV format Ricardo Ribalda Delgado
2016-05-27  8:56 ` Hans Verkuil [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=57480BAC.6050201@xs4all.nl \
    --to=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@osg.samsung.com \
    --cc=ricardo.ribalda@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.