From: Dan Malek <dan@mvista.com>
To: cejka@inf.enst.fr
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: MPC860 and audio codec MC145481 problems
Date: Tue, 18 Sep 2001 19:07:32 -0400 [thread overview]
Message-ID: <3BA7D3B4.6D0C6BB4@mvista.com> (raw)
In-Reply-To: 20010918024908.A18414@inf.enst.fr
cejka@inf.enst.fr wrote:
> .... The problem
> is that both clock signals MCLK/BCLKR/BCLKT and FSR/FST has to be generated
> by PowerPC and there is none input sync signal into PowerPC.
You're not going to be very happy with this design. I doubt you
will be able to generate these clocks in software with the precision
necessary to drive the audio codec. Further, if you do this in
software you aren't likely to have much CPU available for any other
task.
I've worked on a couple of designs that use a Crystal codec,
connected to the TDM interface. This requires minimal CPU
intervention as the audio I/O is handled by the CPM using DMA.
The driver is in the MontaVista HHL distribution, and I'm
currently rewriting it to fit into the linuxppc_2_4 tree.
Good Luck.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-09-18 23:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-18 0:49 MPC860 and audio codec MC145481 problems cejka
2001-09-18 23:07 ` Dan Malek [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=3BA7D3B4.6D0C6BB4@mvista.com \
--to=dan@mvista.com \
--cc=cejka@inf.enst.fr \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).