From: John Bonesio <bones@secretlab.ca>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Grant Likely <grant.likely@secretlab.ca>,
alsa-devel@alsa-project.org,
Eric Millbrandt <emillbrandt@dekaresearch.com>
Subject: Re: MPC5200/WM9712 mute problem
Date: Fri, 07 Aug 2009 07:48:42 -0700 [thread overview]
Message-ID: <1249656522.5844.89.camel@riker> (raw)
In-Reply-To: <20090807095601.GA8175@rakim.wolfsonmicro.main>
On Fri, 2009-08-07 at 10:56 +0100, Mark Brown wrote:
> On Thu, Aug 06, 2009 at 10:28:41AM -0700, John Bonesio wrote:
>
> > I'm open to more suggestions or thoughts on the approach I've taken so
> > far.
>
> The approach you've been taking sounds reasonable; at this point I'd be
> looking at trying to confirm that the controller is doing what's been
> asked of it. Checking that the CODEC power rails are all within spec
> and looking at other bits in the same register may also be useful.
>
> Is the system otherwise idle when the problem occurs?
Yes the system is idle - just me fiddling with the mute settings.
next prev parent reply other threads:[~2009-08-07 14:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-31 23:08 [PATCH] ASoC: MPC5200: Support for buffer wrap around John Bonesio
2009-08-01 1:57 ` Grant Likely
2009-08-01 9:57 ` Mark Brown
2009-08-01 13:47 ` Jon Smirl
2009-08-01 15:04 ` John Bonesio
2009-08-01 16:30 ` Jon Smirl
2009-08-02 11:49 ` Mark Brown
2009-08-05 16:30 ` [PATCH] ASoC: WM9712 Codec: Workaround an unmute problem (Was: Re: [PATCH] ASoC: MPC5200: Support for buffer wrap around) John Bonesio
2009-08-05 17:03 ` MPC5200/WM9712 mute problem Mark Brown
2009-08-06 17:28 ` John Bonesio
2009-08-07 9:56 ` Mark Brown
2009-08-07 14:48 ` John Bonesio [this message]
2009-08-07 15:16 ` Jon Smirl
2009-08-05 17:16 ` [PATCH] ASoC: WM9712 Codec: Workaround an unmute problem (Was: Re: [PATCH] ASoC: MPC5200: Support for buffer wrap around) Jon Smirl
2009-08-05 17:27 ` Jon Smirl
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=1249656522.5844.89.camel@riker \
--to=bones@secretlab.ca \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=emillbrandt@dekaresearch.com \
--cc=grant.likely@secretlab.ca \
/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