ALSA: Provide a CLOCK_MONOTONIC_RAW timestamp type
A message that is not in the archive (sent off-list or not yet received): [email protected]
At Tue, 8 Jul 2014 16:51:49 +0200,
Quoted 11 lines · Mark Brown
From: Mark Brown <[email protected]>
For applications which need to synchronise with external timebases such as broadcast TV applications the kernel monotonic time is not optimal as it includes adjustments from NTP and so may still include discontinuities 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 typeSNDRV_PCM_TSTAMP_TYPE_MONOTONIC_RAWwhich provides timestamps based on this as an option.
Quoted 5 lines
Reported-by Daniel Thompson <[email protected]>Signed-off-by Mark Brown <[email protected]>---
Mostly an RFC at this point as I don't have hardware to test this week.
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.
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?
thanks,
Takashi
Quoted 70 lines
include/sound/pcm.h | 11 +++++++++-- include/uapi/sound/asound.h | 3 ++- sound/core/pcm_native.c | 12 +++++++++--- 3 files changed, 20 insertions(+), 6 deletions(-)include/sound/pcm.h +9
-2@@ -931,10 +931,17 @@ void snd_pcm_timer_done(struct snd_pcm_substream *substream);static inline void snd_pcm_gettime (struct snd_pcm_runtime *runtime,struct timespec *tv) { -if (runtime->tstamp_type ==SNDRV_PCM_TSTAMP_TYPE_MONOTONIC ) +switch (runtime->tstamp_type) { +case SNDRV_PCM_TSTAMP_TYPE_MONOTONIC :ktime_get_ts (tv); -else +break ; +case SNDRV_PCM_TSTAMP_TYPE_MONOTONIC_RAW : +getrawmonotonic (tv); +break ; +default :getnstimeofday (tv); +break ; + } }/* include/uapi/sound/asound.h +2
-1@@ -462,7 +462,8 @@ struct snd_xfern {enum {SNDRV_PCM_TSTAMP_TYPE_GETTIMEOFDAY =0 ,/* gettimeofday equivalent */ SNDRV_PCM_TSTAMP_TYPE_MONOTONIC ,/* posix_clock_monotonic equivalent */ -SNDRV_PCM_TSTAMP_TYPE_LAST =SNDRV_PCM_TSTAMP_TYPE_MONOTONIC , +SNDRV_PCM_TSTAMP_TYPE_MONOTONIC_RAW ,/* monotonic_raw (no NTP) */ +SNDRV_PCM_TSTAMP_TYPE_LAST =SNDRV_PCM_TSTAMP_TYPE_MONOTONIC_RAW , };/* channel positions */ sound/core/pcm_native.c +9
-3@@ -2540,9 +2540,15 @@ static int snd_pcm_tstamp(struct snd_pcm_substream *substream, int __user *_arg)return -EFAULT ;if (arg <0 || arg >SNDRV_PCM_TSTAMP_TYPE_LAST )return -EINVAL ; - runtime->tstamp_type =SNDRV_PCM_TSTAMP_TYPE_GETTIMEOFDAY ; -if (arg ==SNDRV_PCM_TSTAMP_TYPE_MONOTONIC ) - runtime->tstamp_type =SNDRV_PCM_TSTAMP_TYPE_MONOTONIC ; +switch (runtime->tstamp_type) { +case SNDRV_PCM_TSTAMP_TYPE_MONOTONIC : +case SNDRV_PCM_TSTAMP_TYPE_MONOTONIC_RAW : + runtime->tstamp_type = runtime->tstamp_type; +break ; +default : + runtime->tstamp_type =SNDRV_PCM_TSTAMP_TYPE_GETTIMEOFDAY ; +break ; + }return 0 ; }Signature · 1 line
2.0.0
Quoted 10 lines · Takashi Iwai
Quoted 4 lines · Mark Brown
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 typeSNDRV_PCM_TSTAMP_TYPE_MONOTONIC_RAWwhich 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()withgetrawmonotonic()? 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?
Quoted 4 lines
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).
Quoted 8 lines · Mark Brown
Quoted 6 lines · Takashi Iwai
Quoted 4 lines · Mark Brown
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 typeSNDRV_PCM_TSTAMP_TYPE_MONOTONIC_RAWwhich provides timestamps based on this as an option.
Quoted 7 lines
Quoted 3 lines
This looks good to me. Or, thinking of the original use case, should we just replace
ktime_get_ts()withgetrawmonotonic()? 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).
Quoted 7 lines
Quoted 4 lines
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
Signature · 3 lines
Jaroslav Kysela <[email protected]> Linux Kernel Sound Maintainer ALSA Project; Red Hat, Inc.
At Tue, 08 Jul 2014 21:54:32 +0200,
Quoted 18 lines · Jaroslav Kysela
Quoted 8 lines · Mark Brown
Quoted 6 lines · Takashi Iwai
Quoted 4 lines · Mark Brown
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 typeSNDRV_PCM_TSTAMP_TYPE_MONOTONIC_RAWwhich provides timestamps based on this as an option.Quoted 7 lines
Quoted 3 lines
This looks good to me. Or, thinking of the original use case, should we just replace
ktime_get_ts()withgetrawmonotonic()? 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?
Quoted 6 lines
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).
Agreed, it's better to have a separate type, then. I'm going to take the patch to for-next branch.
Quoted 9 lines
Quoted 7 lines
Quoted 4 lines
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..
Yeah, the wall clock stuff might work. But I forgot the detailed requirement. Let's see whether it suffices for V4L guys.
thanks,
Takashi
Quoted 9 lines · Takashi Iwai
Quoted 7 lines · Mark Brown
For applications which need to synchronise with external timebases such as broadcast TV applications the kernel monotonic time is not optimal as it includes adjustments from NTP and so may still include discontinuities 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 typeSNDRV_PCM_TSTAMP_TYPE_MONOTONIC_RAWwhich provides timestamps based on this as an option.
Quoted 3 lines
This looks good to me. Or, thinking of the original use case, should we just replace
ktime_get_ts()withgetrawmonotonic()? The MONOTONIC mode is really to be monotonic.
This would break any applications that relate these timestamps to their own timestamps from clock_gettime(CLOCK_MONOTONIC).
Regards,
Clemens