From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: spi codec names in machine drivers Date: Thu, 31 Mar 2011 09:30:13 +0900 Message-ID: <20110331003012.GE21487@opensource.wolfsonmicro.com> References: <20110330212016.GC20496@opensource.wolfsonmicro.com> <20110331001118.GC21487@opensource.wolfsonmicro.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from opensource2.wolfsonmicro.com (opensource.wolfsonmicro.com [80.75.67.52]) by alsa0.perex.cz (Postfix) with ESMTP id 940511039FD for ; Thu, 31 Mar 2011 02:30:05 +0200 (CEST) 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: Mike Frysinger Cc: alsa-devel@alsa-project.org, Liam Girdwood List-Id: alsa-devel@alsa-project.org On Wed, Mar 30, 2011 at 08:15:14PM -0400, Mike Frysinger wrote: > but back to the original question, how is it working today ? :) i > want to make sure the current Blackfin machine drivers are written > correctly, and the boards i readily have access to are either AC97 or > I2C, so it's difficult for me to boot up and verify myself. This is the common problem with SPI codecs, they're very rarely used so not frequently tested.