From: Jaroslav Kysela <perex@perex.cz>
To: Mark Brown <broonie@kernel.org>, Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org,
Daniel Thompson <daniel.thompson@linaro.org>
Subject: Re: [PATCH] ALSA: Provide a CLOCK_MONOTONIC_RAW timestamp type
Date: Tue, 08 Jul 2014 21:54:32 +0200 [thread overview]
Message-ID: <53BC4C78.5030702@perex.cz> (raw)
In-Reply-To: <20140708160036.GA30458@sirena.org.uk>
Date 8.7.2014 18:00, Mark Brown wrote:
> On Tue, Jul 08, 2014 at 05:00:26PM +0200, Takashi Iwai wrote:
>> Mark Brown wrote:
>
>>> due to that. A raw monotonic time which does not include any adjustments
>>> is available in the kernel from getrawmonotonic() so provide userspace with
>>> a new timestamp type SNDRV_PCM_TSTAMP_TYPE_MONOTONIC_RAW which provides
>>> timestamps based on this as an option.
>
>> This looks good to me. Or, thinking of the original use case, should
>> we just replace ktime_get_ts() with getrawmonotonic()? The MONOTONIC
>> mode is really to be monotonic.
>
> I'm totally OK with that as well if people don't mind that, I just added
> a new clock as the most conservative option. I can easily respin the
> patch for this if you prefer?
Note that the silent change would break the timestamp compatibility,
because monotonic timestamp is used in alsa-lib by default. I would
prefer to add a new type as originaly proposed and allow to choose
between NTP monotonic and raw monotonic. Also the network timestamp
might allow better synchronization for network apps (not sure about the
real usage now, but we're working on an universal framework).
>> While we're at it: there's been long-standing request from V4L guys
>> for improving the timestamps to sync with video streams. I suggested
>> to add a new mode that can be set by the driver. Worth to consider
>> it, too?
>
> Does the wall clock stuff address that? I've no objection to adding a
> further type if the existing ones (and this one aren't sufficient).
I'm curious about requested sync, too..
Jaroslav
--
Jaroslav Kysela <perex@perex.cz>
Linux Kernel Sound Maintainer
ALSA Project; Red Hat, Inc.
next prev parent reply other threads:[~2014-07-08 19:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1404831109-8008-1-git-send-email-broonie@kernel.org>
2014-07-08 15:00 ` [PATCH] ALSA: Provide a CLOCK_MONOTONIC_RAW timestamp type Takashi Iwai
2014-07-08 16:00 ` Mark Brown
2014-07-08 19:54 ` Jaroslav Kysela [this message]
2014-07-09 11:02 ` Takashi Iwai
2014-07-08 17:01 ` Clemens Ladisch
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=53BC4C78.5030702@perex.cz \
--to=perex@perex.cz \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=daniel.thompson@linaro.org \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.