linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@mvista.com>
To: Kyle Harris <kharris@nexus-tech.net>
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: sound driver on mpc823
Date: Wed, 18 Apr 2001 18:49:48 -0400	[thread overview]
Message-ID: <3ADE1A0C.EF3975DF@mvista.com> (raw)
In-Reply-To: 3ADE01A6.CB30230E@nexus-tech.net


Kyle Harris wrote:

> ....But
> I'm not sure exactly how the CPM correlates the RAM entries to buffer
> descriptors (e.g., does it advance buffer descriptors when the RAM entry
> changes).

They don't relate.  The TDM is an autonomous bit mux that moves
bits between the TDM I/O and the communication channels.  The TDM
RAM indicates where the bits are in the TDM I/O stream, how many
there are, and to which communication channel they are connected.
For example, you can tell the TDM there are three bits in every
major frame at offset 19 that belong to SMC2, and tell the SMC2 to
communicate with 8-bit data.  The TDM will pack three bits at a time
to the SMC, and when the SMC gets its eight bits it will do whatever
protocol is appropriate in the SMC and move the data to the buffer.
Any remaining bits between the TDM and the SMC are then used to start
the next 8-bits to the SMC.

The often more confusing part (but it really isn't :-), and very
necessary part is how the communication channel synchronizes to the
TDM frame.  Although it looks like there is lots to read in the
CPM and communication sections of the manual, the words are actually
quite few and very critical to understand.  There is a ton of
information in that manual that you have to understand, and don't
skip one word :-).

I have a telecom/telemetry background, so I guess I can apply that
application experience and make some sense out of the CPM/TDM a
little more easily :-).

Good Luck.


	-- Dan

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2001-04-18 22:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-18 18:29 sound driver on mpc823 Kyle Harris
2001-04-18 20:34 ` Dan Malek
2001-04-18 21:05   ` Kyle Harris
2001-04-18 22:49     ` 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=3ADE1A0C.EF3975DF@mvista.com \
    --to=dan@mvista.com \
    --cc=kharris@nexus-tech.net \
    --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).