public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Philippe De Muyter <phdm@macq.eu>
To: linux-media@vger.kernel.org
Subject: UTC timestamps in v4l2 buffers
Date: Fri, 8 Jan 2021 13:53:34 +0100	[thread overview]
Message-ID: <20210108125334.GA30740@frolo.macqel> (raw)

Hello,

I need to have the v4l2 buffers of my camera sensor timestamped with a
precise (1ms) UTC timestamp, in order to be able to match images from cameras
from several computers (that are of course synchronised with NTP, GPS or PTP).

While I had that some years ago and still have in computers running
freescale's 4.1.15 port for imx6q, I have now discovered that 8 years ago
a decision has been taken by the v4l2 maintainers to switch the timestamp
of the v4l2 buffers to CLOCK_MONOTONIC, which is useless when one needs
to synchronise timestamps of images taken by cameras on different computers,
which of course were not booted at the same time.

At that time a new flag "V4L2_BUF_FLAG_TIMESTAMP_MONOTONIC" was introduced
to tell new users that the timestamp was no more the old and not standardized
behaviour for timestamp, but the new CLOCK_MONOTONIC-based timestamp, but
no other flag for UTC or way to choose which kind of timestamp one wants.

Are there since then new standardized or work-in-progess flag to tell users
that the timestamp is UTC, and way to ask the camera-acquisistion driver to
give that UTC timestamp instead of the CLOCK_MONOTONIC one ?

Best regards.

Philippe

-- 
Philippe De Muyter +32 2 6101532 Macq SA rue de l'Aeronef 2 B-1140 Bruxelles

             reply	other threads:[~2021-01-08 13:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-08 12:53 Philippe De Muyter [this message]
2021-01-28 20:14 ` UTC timestamps in v4l2 buffers Nicolas Dufresne
2021-01-28 22:00   ` Philippe De Muyter

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=20210108125334.GA30740@frolo.macqel \
    --to=phdm@macq.eu \
    --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