From: Geoffrey Wossum <geoffrey@pager.net>
To: alsa-devel@alsa-project.org
Subject: Re: AT32AP7000 (AVR32) + WM8510
Date: Tue, 27 May 2008 17:26:10 -0500 [thread overview]
Message-ID: <200805271726.10331.geoffrey@pager.net> (raw)
In-Reply-To: <20080527184525.GA19124@sirena.org.uk>
On Tuesday 27 May 2008 01:45:28 pm Mark Brown wrote:
> On Tue, May 27, 2008 at 10:16:56AM -0500, Geoffrey Wossum wrote:
> > FRAME as well as BCLK. I might give the WM8510 a try as the master
> > again, since I can get the sample rates closer with it.
>
> Let me know how that goes, please.
Works great, now that I know the secret. Pitch is correct now, and sound
quality is improved, especially at rates that the AT32AP7000 couldn't
accurately generate.
> Thanks - as I said previously it's much better if you can include a
> Signed-off-by line in patch submissions in order to allow them to be
> submitted to the mainline kernel, though in the case of fairly obvious
> register access fixes like these it's generally not an obstacle.
I'll try to remember that :)
I'm not doing any input / microphone stuff right now, but the input signal
path seems incorrect. I get the following error message everytime I start
the wm8510 driver:
asoc: no dapm match for Boost Mixer --> Capture Switch --> Capture Boost
Looking at the signal routing in wm8510.c, there seems to also be issues with
the source and destination of the route being reversed.
---
Geoffrey
prev parent reply other threads:[~2008-05-27 22:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-22 16:20 AT32AP7000 (AVR32) + WM8510 Geoffrey Wossum
2008-05-22 19:46 ` Mark Brown
2008-05-22 19:57 ` Geoffrey Wossum
2008-05-22 22:48 ` Mark Brown
2008-05-22 23:11 ` Geoffrey Wossum
2008-05-23 22:56 ` Geoffrey Wossum
2008-05-26 9:45 ` Mark Brown
2008-05-27 15:16 ` Geoffrey Wossum
2008-05-27 18:45 ` Mark Brown
2008-05-27 22:26 ` Geoffrey Wossum [this message]
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=200805271726.10331.geoffrey@pager.net \
--to=geoffrey@pager.net \
--cc=alsa-devel@alsa-project.org \
/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