From: Hans de Goede <hdegoede@redhat.com>
To: "Frank Schäfer" <fschaefer.oss@googlemail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH] libv4lconvert: clarify the behavior and resulting restrictions of v4lconvert_convert()
Date: Sun, 07 Oct 2012 15:05:03 +0200 [thread overview]
Message-ID: <50717DFF.8000004@redhat.com> (raw)
In-Reply-To: <1349282919-15332-1-git-send-email-fschaefer.oss@googlemail.com>
Hi Frank,
Thanks for all your work on this. I'm afraid that atm I'm very busy
with work, so I don't have time to review your patches. I hope to
find some time for this next weekend...
Regards,
Hans
On 10/03/2012 06:48 PM, Frank Schäfer wrote:
> Signed-off-by: Frank Schäfer <fschaefer.oss@googlemail.com>
> ---
> lib/include/libv4lconvert.h | 20 ++++++++++++++++++--
> 1 Datei geändert, 18 Zeilen hinzugefügt(+), 2 Zeilen entfernt(-)
>
> diff --git a/lib/include/libv4lconvert.h b/lib/include/libv4lconvert.h
> index 167b57d..509655e 100644
> --- a/lib/include/libv4lconvert.h
> +++ b/lib/include/libv4lconvert.h
> @@ -89,8 +89,24 @@ LIBV4L_PUBLIC int v4lconvert_needs_conversion(struct v4lconvert_data *data,
> const struct v4l2_format *src_fmt, /* in */
> const struct v4l2_format *dest_fmt); /* in */
>
> -/* return value of -1 on error, otherwise the amount of bytes written to
> - dest */
> +/* This function does the following conversions:
> + - format conversion
> + - cropping
> + if enabled:
> + - processing (auto whitebalance, auto gain, gamma correction)
> + - horizontal/vertical flipping
> + - 90 degree (clockwise) rotation
> +
> + NOTE: the last 3 steps are enabled/disabled depending on
> + - the internal device list
> + - the state of the (software emulated) image controls
> +
> + Therefore this function should
> + - not be used when getting the frames from libv4l
> + - be called only once per frame
> + Otherwise this may result in unintended double conversions !
> +
> + Returns the amount of bytes written to dest an -1 on error */
> LIBV4L_PUBLIC int v4lconvert_convert(struct v4lconvert_data *data,
> const struct v4l2_format *src_fmt, /* in */
> const struct v4l2_format *dest_fmt, /* in */
>
next prev parent reply other threads:[~2012-10-07 13:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 16:48 [PATCH] libv4lconvert: clarify the behavior and resulting restrictions of v4lconvert_convert() Frank Schäfer
2012-10-07 13:05 ` Hans de Goede [this message]
2012-10-07 13:56 ` Frank Schäfer
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=50717DFF.8000004@redhat.com \
--to=hdegoede@redhat.com \
--cc=fschaefer.oss@googlemail.com \
--cc=linux-media@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).