All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heikki Lindholm <holindho@cs.helsinki.fi>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: POSIX clocks and ALSA
Date: Mon, 26 Nov 2007 10:42:46 +0200	[thread overview]
Message-ID: <474A8706.1070102@cs.helsinki.fi> (raw)
In-Reply-To: <s5h63zpph0s.wl%tiwai@suse.de>

Takashi Iwai kirjoitti:
> At Mon, 26 Nov 2007 09:59:29 +0200,
> Heikki Lindholm wrote:
>> Jaroslav Kysela kirjoitti:
>>> On Mon, 26 Nov 2007, Heikki Lindholm wrote:
>>>
>>>> Hello,
>>>>
>>>> Some years ago there was some talk about UST support in Linux, but the 
>>>> support never happened. With the hrtimers patch (and I'm not quite sure 
>>>> if even earlier?) CLOCK_MONOTONIC would seem like a fairly good UST time 
>>>> source. What I'd like to see, is a selectable clock for ALSA 
>>>> timestamping, e.g. something like snd_sw_params_clock(..., clockid_t 
>>>> clk). Would this seem plausible? I don't know that much about ALSA 
>>>> internals, so, no idea whether different clocks on different 
>>>> pcms/whatever would quickly turn into an unmanageable mess.
>>> We are aware about this extension and I already proposed an 
>>> implementation. I hope to implement it soon. Timestamps are not used in 
>>> driver internally.
>> I can't seem to google up the proposal. I'd like to read it; was it on 
>> the alsa ml?
> 
> Yes, it was on alsa-devel ML.  At that time I didn't like the proposal
> much because currently there was no real user of timestamps.
> 
> The addition of monolithc clock isn't hard, but it's an API change
> that involves with the kernel-side change.  So let's do it carefully.
> 
> But, honestly, I'm still concerned what to be done first.  Shouldn't
> we discuss about the usefulness of the timestamp at first?  That is,
> whether the current form (API, implementation) is the best or not,
> what kind of user would be, and how it's used.  So far, this feature
> is "simply there"...

IMHO the current API definitely isn't the best possible, but nothing 
better has been available on Linux, so it's a make-do situation. My 
ideal would be something resembling or even 1:1 copying SGI's media 
libraries where every media fragment is timestamped with the UST, and 
the timestamps are the starting time of the media chunk in question 
instead of ending/sometime after time. The problem with implementing the 
SGI API on Linux is that AFAICT no Linux supported/available hardware 
supports such timestamping.

Additionally, it might be nice to be able to add audio clocks as system 
wide clocks, so, that for example I could tell v4l to use timestamps 
from an audio clock instead of the system clock.

Allowing clock selection between CLOCK_REALTIME (for backwards 
compatibility) and CLOCK_MONOTONIC would, however, be a start.

-- Heikki Lindholm

  parent reply	other threads:[~2007-11-26  8:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-26  7:31 POSIX clocks and ALSA Heikki Lindholm
2007-11-26  7:49 ` Jaroslav Kysela
2007-11-26  7:59   ` Heikki Lindholm
2007-11-26  8:06     ` Takashi Iwai
2007-11-26  8:37       ` Jaroslav Kysela
2007-11-26  8:42       ` Heikki Lindholm [this message]
2007-11-26 13:04         ` Jaroslav Kysela
2007-11-26 13:49           ` Takashi Iwai
2007-11-26 14:44             ` Jaroslav Kysela
2007-11-26 16:18           ` Heikki Lindholm
2007-11-26 10:10       ` Heikki Lindholm
2007-11-26 10:15         ` Takashi Iwai
2007-11-26 10:04   ` Heikki Lindholm
2007-11-26 14:51     ` Jaroslav Kysela
2007-11-26 16:04       ` Heikki Lindholm
2007-12-04 16:26         ` Jaroslav Kysela

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=474A8706.1070102@cs.helsinki.fi \
    --to=holindho@cs.helsinki.fi \
    --cc=alsa-devel@alsa-project.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.