From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Geoffrey Wossum <geoffrey@pager.net>
Cc: alsa-devel@alsa-project.org
Subject: Re: AT32AP7000 (AVR32) + WM8510
Date: Mon, 26 May 2008 10:45:24 +0100 [thread overview]
Message-ID: <20080526094523.GA18721@sirena.org.uk> (raw)
In-Reply-To: <200805231756.00609.geoffrey@pager.net>
On Fri, May 23, 2008 at 05:56:00PM -0500, Geoffrey Wossum wrote:
> First, I changed it so the AVR32 provided the BCLK and FRAME. I could never
> get the WM8510 to generate what looked like proper FRAMES. I did continue
> using the WM8510's PLL to generate the DAC clock. With the AVR32 providing
> the clocks, I at least got some noise out of it.
The frame clock rate generated by the WM8510 will be 1/256 of the system
clock, which should be configured to 256 times the sample rate using the
PLL and dividers.
> Finally, I really had to lie in the wm8510 code and say that it supported a
> minimum of 2 channels, and a maximum of 2 channels. This makes sense from
> the data sheet, since it still wants a left and a right channel of data, and
> just throws one away.
Yes, that's right. I've applied your changes to the driver - thanks!
> I had to change the WM8510's format to say that it wanted big endian. Should
> the CODEC (and platform and machine) be setup just to say that it uses
> SNDRV_PCM_FMTBIT_S16 instead of SNDRV_PCM_FMTBIT_S16_LE/BE? Looks from
> sound/pcm.h this should just do the Right Thing.
Yes, it does look reasonable - I'll investigate.
> Like I said before, it generated a 44.1 kHz frame no matter the BCLK divider
> or the word length were set to.
The frame clock is independent of both those options - I assume you are
using a static system clock?
> Thanks for the help! As soon as I get the code cleaned up some, I'll
> contribute the AVR32 platform driver code.
That would be excellent.
next prev parent reply other threads:[~2008-05-26 9:45 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 [this message]
2008-05-27 15:16 ` Geoffrey Wossum
2008-05-27 18:45 ` Mark Brown
2008-05-27 22:26 ` Geoffrey Wossum
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=20080526094523.GA18721@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=geoffrey@pager.net \
/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