From mboxrd@z Thu Jan 1 00:00:00 1970 From: Timur Tabi Subject: Re: Trouble understanding ALSA's DMA buffers Date: Tue, 12 Jun 2007 11:36:33 -0500 Message-ID: <466ECB91.2030609@freescale.com> References: <466DA941.40309@freescale.com> <8d6898730706111329y666c7abdv5b464cbe4e9bb3b@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from de01egw01.freescale.net (de01egw01.freescale.net [192.88.165.102]) by alsa0.perex.cz (Postfix) with ESMTP id A3CCC1037F7 for ; Tue, 12 Jun 2007 18:36:38 +0200 (CEST) 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: Takashi Iwai Cc: alsa-devel@alsa-project.org, Nobin Mathew List-Id: alsa-devel@alsa-project.org Takashi Iwai wrote: > Yes. And the "ping-poing" is the case that you have two periods in a > ring buffer. Ok, I understand the 'periods' concept now, thanks. So when/where does ALSA copy data to the DMA buffer? Isn't there supposed to be some kind of callback where ALSA calls the driver and says, "here's some data, please copy it to your DMA buffer?" Or does ALSA do all the copying itself whenever the driver calls snd_pcm_period_elapsed()? -- Timur Tabi Linux Kernel Developer @ Freescale