From: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
To: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
Sakari Ailus <sakari.ailus@iki.fi>,
linux-media@vger.kernel.org, laurent.pinchart@ideasonboard.com,
k.debski@samsung.com
Subject: Re: [PATCH v5.1 3/7] v4l: Add timestamp source flags, mask and document them
Date: Thu, 20 Feb 2014 22:20:59 +0100 [thread overview]
Message-ID: <530671BB.107@gmail.com> (raw)
In-Reply-To: <53066F5E.7020202@gmail.com>
On 02/20/2014 10:10 PM, Sylwester Nawrocki wrote:
>> I would actually be inclined to drop it altogether for this particular
>> timestamp source. But it's up to Laurent.
>
> Yup, the "a small amount of time" concept seems a bit vague here.
> It's not clear how long period it could be and the tolerance would like
> very across the hardware.
Sorry, I meant "would likely vary".
next prev parent reply other threads:[~2014-02-20 21:21 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-15 20:52 [PATCH v5 0/7] Fix buffer timestamp documentation, add new timestamp flags Sakari Ailus
2014-02-15 20:52 ` [PATCH v5 1/7] v4l: Document timestamp behaviour to correspond to reality Sakari Ailus
2014-02-15 20:53 ` [PATCH v5 2/7] v4l: Use full 32 bits for buffer flags Sakari Ailus
2014-02-17 8:46 ` Hans Verkuil
2014-02-23 11:49 ` Hans Verkuil
2014-02-24 15:34 ` Sakari Ailus
2014-02-24 16:02 ` Hans Verkuil
2014-02-24 17:57 ` Laurent Pinchart
2014-02-24 16:13 ` Kamil Debski
2014-02-25 11:44 ` 'Sakari Ailus'
2014-02-25 12:02 ` Hans Verkuil
2014-02-15 20:53 ` [PATCH v5 3/7] v4l: Add timestamp source flags, mask and document them Sakari Ailus
2014-02-17 8:54 ` Hans Verkuil
2014-02-17 23:29 ` Sakari Ailus
2014-02-20 19:41 ` [PATCH v5.1 " Sakari Ailus
2014-02-20 20:36 ` Hans Verkuil
2014-02-20 21:10 ` Sylwester Nawrocki
2014-02-20 21:20 ` Sylwester Nawrocki [this message]
2014-02-21 9:51 ` Sakari Ailus
2014-02-20 23:30 ` Laurent Pinchart
2014-02-21 7:17 ` Hans Verkuil
2014-02-21 9:31 ` Sakari Ailus
2014-02-21 11:58 ` Laurent Pinchart
2014-02-21 13:04 ` Sakari Ailus
2014-02-21 13:19 ` Laurent Pinchart
2014-02-23 10:40 ` [PATCH v5.2 " Sakari Ailus
2014-02-23 11:36 ` Hans Verkuil
2014-02-25 13:09 ` [PATCH v5 " Kamil Debski
2014-02-26 0:09 ` 'Sakari Ailus'
2014-02-15 20:53 ` [PATCH v5 4/7] uvcvideo: Tell the user space we're using start-of-exposure timestamps Sakari Ailus
2014-02-17 0:51 ` Laurent Pinchart
2014-02-15 20:53 ` [PATCH v5 5/7] exynos-gsc, m2m-deinterlace, mx2_emmaprp: Copy v4l2_buffer data from src to dst Sakari Ailus
2014-02-25 13:08 ` Kamil Debski
2014-02-15 20:53 ` [PATCH v5 6/7] v4l: Copy timestamp source flags to destination on m2m devices Sakari Ailus
2014-02-25 13:08 ` Kamil Debski
2014-02-15 20:53 ` [PATCH v5 7/7] v4l: Document timestamp buffer flag behaviour Sakari Ailus
2014-02-15 21:03 ` Hans Verkuil
2014-02-16 17:50 ` Sakari Ailus
2014-02-17 0:56 ` Laurent Pinchart
2014-02-17 8:43 ` Hans Verkuil
2014-02-17 23:32 ` Sakari Ailus
2014-02-17 23:33 ` Sakari Ailus
2014-02-20 19:42 ` [PATCH v5.1 " Sakari Ailus
2014-02-20 20:25 ` Hans Verkuil
2014-02-23 10:39 ` Sakari Ailus
2014-02-23 11:45 ` [PATCH v5 " Hans Verkuil
2014-02-25 17:08 ` Sakari Ailus
2014-02-25 17:28 ` Hans Verkuil
2014-02-26 0:04 ` Sakari Ailus
2014-02-26 0:07 ` Hans Verkuil
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=530671BB.107@gmail.com \
--to=sylvester.nawrocki@gmail.com \
--cc=hverkuil@xs4all.nl \
--cc=k.debski@samsung.com \
--cc=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