From mboxrd@z Thu Jan 1 00:00:00 1970 From: Timur Tabi Subject: Re: hw_params function and OSS emulation Date: Wed, 22 Aug 2007 16:08:49 -0500 Message-ID: <46CCA5E1.5050704@freescale.com> References: <46CB2BB4.9060808@freescale.com> <46CC480F.7090604@freescale.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from de01egw02.freescale.net (de01egw02.freescale.net [192.88.165.103]) by alsa0.perex.cz (Postfix) with ESMTP id 39C551037FB for ; Wed, 22 Aug 2007 23:08:54 +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, Trent Piepho List-Id: alsa-devel@alsa-project.org Takashi Iwai wrote: > The buffer allocation in prepare callback would actually do work. > I've never mentioned that it doesn't work. It's just not > recommended, simply because the prepare is called more often than > hw_params even without changing the parameters. What is the driver supposed to do on the second call to .prepare()? In other words, what is the point of calling it multiple times in a row? Once my driver is prepared to start, how could it become more prepared? -- Timur Tabi Linux Kernel Developer @ Freescale