From: lokowich <lokowich@acdstar.com>
To: Timur Tabi <timur@freescale.com>
Cc: ALSA-devel <alsa-devel@alsa-project.org>
Subject: Re: MPC5200 I2S driver for ASoC
Date: Wed, 01 Aug 2007 14:16:23 -0500 [thread overview]
Message-ID: <46B0DC07.4050000@acdstar.com> (raw)
In-Reply-To: <46B0C89D.50704@freescale.com>
Timur Tabi wrote:
> lokowich wrote:
>
>> I'm integrating a ALSA driver for an MPC5200 into the ASoC layer,
>> similar to my successful effort for a PXA255 board.
>>
>
> Can you provide your code? I'm working on ASoC support for another MPC SOC, so we need to
> synchronize our development.
>
Yes, I presume you mean using git into the ALSA branch. I need to
get more familiar with git, and follow the appropriate coding
conventions before it's ready. Any guidance will be appreciated.
> I'm modeling the
> DMA and ALSA interfaces per ac97mgt driver found in the Lite5200B BSP,
> rather than the BestComm API example in the 2.4 kernel. The
> speaker-test with 400Hz sine wave is working, but has a slight audible
> jitter. A wav file output using aplay produces white noise.
>
>
> What kind of audio samples are you trying to play? Since the MPC5200 is typically
> big-endian, you probably can only play S16_BE samples instead of S16_LE samples.
>
>
Yes! I had enabled the S16_BE format in my codec/i2s/pcm driver,
but naively thought ALSA would handle the rest. Converted my test
file to S16_BE and it sounds much closer to the original. Thanks!
Found the "jitter" is due to a FIFO overflow. I'm using same alarm
(0x120) and granularity (4) common to 2.4 I2S and ac97 drivers. Is
there a more appropriate setting for 16-bit, 2-channel, 44.1kHz audio?
Also, can we chat about SDRAM problems on 5200B outside of this forum?
This email was Anti Virus checked by Astaro Security Gateway. http://www.astaro.com
next prev parent reply other threads:[~2007-08-01 19:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 17:33 MPC5200 I2S driver for ASoC lokowich
2007-08-01 17:53 ` Timur Tabi
2007-08-01 19:16 ` lokowich [this message]
2007-08-01 19:45 ` Timur Tabi
2007-08-01 19:41 ` Jon Smirl
2007-08-01 21:03 ` lokowich
2007-08-01 21:20 ` Timur Tabi
2007-08-05 0:11 ` 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=46B0DC07.4050000@acdstar.com \
--to=lokowich@acdstar.com \
--cc=alsa-devel@alsa-project.org \
--cc=timur@freescale.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).