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: Fri, 27 Aug 2010 20:14:30 +0100 [thread overview]
Message-ID: <20100827191428.GB6666@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <AANLkTikr3rpij1FuKAQrwR0U8kpJUnKzfVJEzeYeGEsk@mail.gmail.com>
On Fri, Aug 27, 2010 at 03:32:16PM +0200, Manuel Lauss wrote:
> I've found another AC97-related issue on another board (DB1300):
> With AC97 enabled, the device warning doesn't appear but my ethernet
> is gone instead:
This seems like some sort of pin mux issue or something driver specific?
I'm having a hard time thinking of anything ASoC could do that'd cause
this, but I don't know how the two subsystems might interact on this
system or au1x in general.
In any case I'm tempted to apply what we've got here since while there
are still issues it's all au1x (and seemingly AC97) specific and it
improves the situation for that platform - we can continue to work on
the remaining problems without re-reviewing this code again. Liam, does
that seem reasonable?
next prev parent reply other threads:[~2010-08-27 19:14 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 [this message]
2010-08-27 22:43 ` Manuel Lauss
2010-08-27 23:43 ` Mark Brown
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=20100827191428.GB6666@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).