public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
To: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
Cc: linux-media <linux-media@vger.kernel.org>
Subject: Re: RFC> multi-crop (was: Multiple Rectangle cropping)
Date: Thu, 05 Sep 2013 23:44:14 +0200	[thread overview]
Message-ID: <5228FB2E.5050503@gmail.com> (raw)
In-Reply-To: <CAPybu_0J63XVEv=EPHbarn8EH9H5okEBbihaiZSOdwggkvV5xQ@mail.gmail.com>

On 09/05/2013 11:10 PM, Ricardo Ribalda Delgado wrote:
> Hello

Hi,

>   I am working porting a industrial camera driver to v4l. So far I have
> been able to describe most of the old functionality with v4l
> equivalents. The only thing that I am missing is multi cropping.
>
> The sensor (both a cmosis and a ccd chips) supports skipping lines
> from up to 8 regions. This increases the readout speed up to 50%,
> which is critical for the application.
>
> Unfortunately I have no way to describe multiple cropping areas in
> v4l. I am thinking about creating a new API/extending and old one for
> this.
>
> Any suggestion before I start? Have you faced also this problem? How
> did you solve it?

A similar issue has been raised during discussions on the camera auto
focus rectangle selection API. While defining need selection targets [1]
it was also proposed to convert one of the struct v4l2_selection reserved
fields into an index field, which would indicate one rectangle of some
set of rectangles supported by a driver. Then there could be a v4l2
bitmask control to determine which rectangles are currently valid/in use.

Would something like this be relevant to your problem ?

> I am planning to go to the Edinburgh mini summit, maybe we could add
> this to the agenda (if you consider that it is worth the time, of
> course)

It definitely sounds like a good topic to discuss at the mini summit,
unless it gets resolved until then. ;-)

[1] http://www.spinics.net/lists/linux-media/msg64499.html

--
Regards,
Sylwester

  reply	other threads:[~2013-09-05 21:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-05 21:10 RFC> multi-crop (was: Multiple Rectangle cropping) Ricardo Ribalda Delgado
2013-09-05 21:44 ` Sylwester Nawrocki [this message]
2013-09-06  8:30   ` Ricardo Ribalda Delgado
2013-09-10 21:41     ` Sakari Ailus
2013-09-10 22:05       ` RFC> multi-crop Sylwester Nawrocki
2013-09-11  7:38         ` Ricardo Ribalda Delgado
2013-09-10 22:35     ` RFC> multi-crop (was: Multiple Rectangle cropping) Sakari Ailus
2013-09-11  8:28       ` Ricardo Ribalda Delgado
2013-09-11  8:30         ` [PATCH] RFC: Support for multiple selections Ricardo Ribalda Delgado
2013-09-11  9:04           ` Hans Verkuil
2013-09-11  9:34             ` Ricardo Ribalda Delgado
2013-09-11 10:49               ` Hans Verkuil
2013-09-11 12:13                 ` Ricardo Ribalda Delgado
2013-09-11 13:02                   ` Hans Verkuil
2013-09-12 17:09                     ` Ricardo Ribalda Delgado
2013-09-12 17:10         ` [PATCH] RFCv2: " Ricardo Ribalda Delgado

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=5228FB2E.5050503@gmail.com \
    --to=sylvester.nawrocki@gmail.com \
    --cc=linux-media@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox