From mboxrd@z Thu Jan 1 00:00:00 1970 From: Heikki Lindholm Subject: Re: POSIX clocks and ALSA Date: Mon, 26 Nov 2007 09:59:29 +0200 Message-ID: <474A7CE1.7080904@cs.helsinki.fi> References: <474A763E.7090001@cs.helsinki.fi> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from emh06.mail.saunalahti.fi (emh06.mail.saunalahti.fi [62.142.5.116]) by alsa0.perex.cz (Postfix) with ESMTP id DA8D624776 for ; Mon, 26 Nov 2007 08:59:30 +0100 (CET) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Jaroslav Kysela Cc: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org 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? -- Heikki Lindholm