From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Manuel Lauss <manuel.lauss@googlemail.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Ian Lartey <ian@opensource.wolfsonmicro.com>,
"alsa-devel@vger.kernel.org" <alsa-devel@vger.kernel.org>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH v5] ASoC/2.6.37: fix au1x platform
Date: Sat, 28 Aug 2010 00:43:28 +0100 [thread overview]
Message-ID: <20100827234315.GA8619@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <AANLkTimNHTDFp2g8c_s5hDc_3D9QPaeWDWcFr9UCPn9-@mail.gmail.com>
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.
next prev parent reply other threads:[~2010-08-27 23:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-26 12:53 [PATCH v5] ASoC/2.6.37: fix au1x platform Manuel Lauss
2010-08-27 12:51 ` Liam Girdwood
2010-08-27 13:07 ` Mark Brown
2010-08-27 13:32 ` Manuel Lauss
2010-08-27 19:14 ` Mark Brown
2010-08-27 22:43 ` Manuel Lauss
2010-08-27 23:43 ` Mark Brown [this message]
2010-08-31 11:01 ` Mark Brown
2010-09-10 15:00 ` Manuel Lauss
2010-09-10 15:03 ` Mark Brown
2010-10-13 9:33 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100827234315.GA8619@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=alsa-devel@vger.kernel.org \
--cc=ian@opensource.wolfsonmicro.com \
--cc=lrg@slimlogic.co.uk \
--cc=manuel.lauss@googlemail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).