From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Courtier-Dutton Subject: Re: RFC: Add support for monotonic clock for 2.6 Date: Wed, 07 Mar 2007 22:33:25 +0000 Message-ID: <45EF3DB5.3090008@superbug.co.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from anchor-post-30.mail.demon.net (anchor-post-30.mail.demon.net [194.217.242.88]) by alsa0.perex.cz (Postfix) with ESMTP id B932C2432F for ; Wed, 7 Mar 2007 23:33:26 +0100 (CET) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@lists.sourceforge.net Errors-To: alsa-devel-bounces@lists.sourceforge.net To: Takashi Iwai Cc: ALSA development , Jaroslav Kysela List-Id: alsa-devel@alsa-project.org Takashi Iwai wrote: > At Tue, 27 Feb 2007 15:52:41 +0100 (CET), > Jaroslav Kysela wrote: >> Hi, >> >> in 2.6 kernels, we can use ktime_get_ts() function to get >> monotonic time which can be used for PCM timestamps. I would propose to >> reuse the SNDRV_PCM_IOCTL_TSTAMP ioctl to enable using of monotonic clock. >> The "enable" (int) argument might mean: >> >> 0: standard clock - getnstimeofday() >> 1: standard clock - getnstimeofday() - for "compatibility" >> 2: monotonic clock - ktime_get_ts() > > Good to add a new feature... but is there any user of this PCM > timestamp so far? I see some good purposes but rarely seen in the > reality, unfortunately... > > > Takashi > There are some good applications for it, but I have not got round to writing them yet! James ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV