From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: linux-media@vger.kernel.org
Subject: Re: [yavta PATCH v3 00/11] Timestamp source and mem-to-mem device support
Date: Wed, 16 Apr 2014 20:21:54 +0200 [thread overview]
Message-ID: <3531905.nrTue8ouRr@avalon> (raw)
In-Reply-To: <1397309043-8322-1-git-send-email-sakari.ailus@iki.fi>
Hi Sakari,
Thank you for the patches.
On Saturday 12 April 2014 16:23:52 Sakari Ailus wrote:
> Hi,
>
> This is the third version of the timestamp source and mem-to-mem device
> support patchset.
>
> Change since v2:
>
> - struct device type remains enum v4l2_buf_type
>
> - Added a struct which contains the 1:1 mapping between V4L2 buffer type,
> verbose textual representation of it (which already existed), and a
> command line option. A function for converting the former to the first is
> provided as well.
>
> - struct device is no longer manipulated in main(), with the few exceptions
> that existed before the patchset. Instead, functions are provided to
> access it.
>
> - -Q (--queue-type) has been replaced with -B (--buffer-type).
>
> - Added a patch to shorten the timestamp type names.
>
> - Added another patch to shorten the string printed for each dequeued
> buffer.
>
> - Invalid buffer types are rejected now by yavta.
>
> - Removed useless use of else.
Applied with whitespace fixes and the following change to 07/11.
@@ -867,6 +868,9 @@ static int video_queue_buffer(struct device *dev,
buf.type = dev->type;
buf.memory = dev->memtype;
- if (dev->type == V4L2_BUF_TYPE_VIDEO_OUTPUT)
+ if (video_is_output(dev))
buf.flags = dev->buffer_output_flags;
if (video_is_mplane(dev)) {
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-04-16 18:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-12 13:23 [yavta PATCH v3 00/11] Timestamp source and mem-to-mem device support Sakari Ailus
2014-04-12 13:23 ` [yavta PATCH v3 01/11] Separate device object initialisation and opening Sakari Ailus
2014-04-12 13:23 ` [yavta PATCH v3 02/11] Provide functions for setting the buffer type and checking its validity Sakari Ailus
2014-04-12 13:23 ` [yavta PATCH v3 03/11] Separate querying capabilities and determining buffer queue type Sakari Ailus
2014-04-12 13:23 ` [yavta PATCH v3 04/11] Make struct for buffer type and name mapping usable elsewhere Sakari Ailus
2014-04-12 13:23 ` [yavta PATCH v3 05/11] Provide -B option for setting the buffer type Sakari Ailus
2014-04-12 13:23 ` [yavta PATCH v3 06/11] Allow passing file descriptors to yavta Sakari Ailus
2014-04-12 13:23 ` [yavta PATCH v3 07/11] Timestamp source for output buffers Sakari Ailus
2014-04-12 13:24 ` [yavta PATCH v3 08/11] Print timestamp type and source for dequeued buffers Sakari Ailus
2014-04-12 13:24 ` [yavta PATCH v3 09/11] Shorten dequeued buffer info print Sakari Ailus
2014-04-12 13:24 ` [yavta PATCH v3 10/11] Support copy timestamps Sakari Ailus
2014-04-12 13:24 ` [yavta PATCH v3 11/11] Set timestamp for output buffers if the timestamp type is copy Sakari Ailus
2014-04-16 18:21 ` Laurent Pinchart [this message]
2014-04-16 18:23 ` [yavta PATCH v3 00/11] Timestamp source and mem-to-mem device support Sakari Ailus
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=3531905.nrTue8ouRr@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@iki.fi \
/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