From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: Driver for a codec with built-in DSP for MP3 playback Date: Mon, 15 Mar 2010 14:14:05 +0000 Message-ID: <20100315141404.GA13878@sirena.org.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from cassiel.sirena.org.uk (cassiel.sirena.org.uk [80.68.93.111]) by alsa0.perex.cz (Postfix) with ESMTP id 2CBEF10382C for ; Mon, 15 Mar 2010 15:14:06 +0100 (CET) Content-Disposition: inline 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: Dajun Chen Cc: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org On Mon, Mar 15, 2010 at 02:02:39PM +0000, Dajun Chen wrote: > I am wondering where to find the guidances of developing a device driver for > a codec device which has a built-in DSP for MP3 (and tracks in other format) > playback and recording? OOI which device? I'm not sure what you mean by guidance here. The standard thing would be to do it as a regular CODEC driver with a custom interface for userspace (eg, gstreamer) to talk to. The best way of handling DAPM will depend on implementation but probably representing the output of the DSP as an input pin will be easiest.