From: Liam Girdwood Subject: Re: ASoC and a codec that can't be controlled Date: Mon, 28 May 2007 13:10:47 +0100 Message-ID: <1180354247.5816.30.camel@a10072.wolfsonmicro.main> References: <46531097.5040600@freescale.com> <1179934677.12071.30.camel@a10072.wolfsonmicro.main> <46574453.10808@freescale.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from opensource.wolfsonmicro.com (unknown [80.75.67.54]) by alsa0.perex.cz (Postfix) with ESMTP id 9E35C2471D for ; Mon, 28 May 2007 14:10:48 +0200 (CEST) In-Reply-To: <46574453.10808@freescale.com> 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: Timur Tabi Cc: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org On Fri, 2007-05-25 at 15:17 -0500, Timur Tabi wrote: > Liam Girdwood wrote: > > > These are used for setting up the dynamic audio power management and > > won't be needed in stand alone mode. > > So if I don't care about power management, can I completely ignore anything with "dapm" in it? Yes. > > Also, do I need a codec driver at all, even if I can't control the codec? That is, can I > do stuff like this: > > static struct snd_soc_device mysoc_snd_devdata = { > .machine = &snd_soc_machine_mysoc, > .platform = &mysoc_soc_platform, > }; > > static struct snd_soc_dai_link mpc8610hpcd_dai = { > .name = "CS4270", > .stream_name = "CS4270", > .cpu_dai = &mysoc_i2s_dai, > .init = mpc8610hpcd_machine_init, > .ops = &mpc8610hpcd_ops, > }; Yes, although my feeling is that a codec "driver" would still be needed to define the capabilities of your codec within the audio subsystem. e.g. supported sample rates, interface formats, etc Liam