From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: [PATCH v5] ASoC/2.6.37: fix au1x platform Date: Sat, 28 Aug 2010 00:43:28 +0100 Message-ID: <20100827234315.GA8619@opensource.wolfsonmicro.com> References: <1282827231-17323-1-git-send-email-manuel.lauss@googlemail.com> <1282913484.3025.25.camel@odin> <1365302F-4C5D-4075-8D38-94DEEEF2583E@opensource.wolfsonmicro.com> <20100827191428.GB6666@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 ABC5B24332 for ; Sat, 28 Aug 2010 01:43:16 +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: Manuel Lauss Cc: "alsa-devel@alsa-project.org" , Ian Lartey , "alsa-devel@vger.kernel.org" , Liam Girdwood List-Id: alsa-devel@alsa-project.org On Sat, Aug 28, 2010 at 12:43:27AM +0200, Manuel Lauss wrote: > On Fri, Aug 27, 2010 at 9:14 PM, Mark Brown > > This seems like some sort of pin mux issue or something driver specific? > No, no. The drivers don't touch pin config. It is related to the AC97 parts > of ASoC, however. Somewhere memory gets overwritten which causes > the DB1300's ethernet and the DB1200's reset code to fail. I'll see if I > can find out exactly what's going on. There was something similar in > the ASoC AC97 code 1-2 years ago which caused linked list corruption, > but Liam fixed that pretty quickly. This sounds like the driver specifics I was talking about. ASoC doesn't get involved in anything that's likely to affect memory much in a way that'd only show up on one system, and I'd expect things that did go wrong to have a much less specific effect. It could possibly be the generic AC97 bodge (at which point it's specific to ac97.c) but it's unlikely to be ASoC itself.