From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: ALSA SoC on Android problems Date: Fri, 24 Jun 2011 13:34:14 +0100 Message-ID: <20110624123413.GA19804@sirena.org.uk> References: <4E035DCA.9010409@csr.com> 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 92251103AFD for ; Fri, 24 Jun 2011 14:34:16 +0200 (CEST) Content-Disposition: inline In-Reply-To: <4E035DCA.9010409@csr.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: Marco Sinigaglia Cc: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org On Thu, Jun 23, 2011 at 04:37:46PM +0100, Marco Sinigaglia wrote: > I am quite sure that the kernel does not find/setup the WM9714. > Assuming that is the kernel that has to configure it, do I have to setup > something? > I can see that, on linux-2.6.35/sound/soc/codecs/wm9713.c, the > wm9713_soc_probe function is not call. Nevertheless, the smdk_wm9713.c > does run the smdk_init without errors. You need to write a machine driver for your board and you need to ensure that all the ASoC devices are registered on your system. Defining DEBUG at the top of soc-core.c will make ASoC much more verbose about the probe process.