linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Eric N. Johnson (ACD)" <ejohnson@acdstar.com>
To: linuxppc-embedded@ozlabs.org
Subject: (no subject)
Date: Tue, 12 Apr 2005 14:38:20 -0500	[thread overview]
Message-ID: <6.2.1.2.1.20050412143653.02ae7720@mail.int.acdstar.com> (raw)

Has anyone been able to use an I2S audio DAC connected to a Programmable 
Serial Controllers (PSC) on the Freescale MPC5200 CPU working under Linux?

The kernel included in the DENX ELDK v3.1.1 has two drivers:
   i2s_ring.c and i2s.c.
The ring driver appears to be RX only, and the i2s.c driver causes the FEC 
ethernet to hang at startup.  I've read some previous mailing list messages 
that suggest there are issues with bestcomm and i2s support.

We've tried adapting the i2s_ring.c driver for our needs.  By default, it 
only has a receive task.  It partially initializes the port, and we see 
appropriate waveforms on the MCLK, CLK, and FRAME lines, but have not been 
able to transmit data.

The stock i2s.c driver hung the boot sequence, but if we comment out the 
bestcomm startup code, it at least completes the boot cycle.  Again we see 
appropriate waveforms on the MCLK, CLK, and FRAME lines.  If we feed data 
to the device (after performing the port setup IOCTLs), we see a 750 us 
burst of data every 45 ms or so.

Is it feasible to send 44.1 or 48 KHz 16-bit audio this way or is the PSC 
only usable for lower data rate applications?

Thank you,
Eric
------------------------------------
Eric Johnson, Electrical Engineer
Advanced Communication Design
   7901 12th Avenue South
   Bloomington, MN 55425
Ph: 952-854-4000  Fax: 952-854-5774

             reply	other threads:[~2005-04-12 19:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-12 19:38 Eric N. Johnson (ACD) [this message]
2005-04-12 21:13 ` (no subject) Wolfgang Denk
2005-04-12 22:46   ` MPC5200 I2S driver Eric N. Johnson (ACD)
2005-04-12 23:40     ` Wolfgang Denk
2005-04-13 20:23     ` Hans Thielemans
  -- strict thread matches above, loose matches on Subject: below --
2021-12-27 14:59 [PATCH v2 2/3] arm64: Support huge vmalloc mappings Kefeng Wang
2021-12-27 17:35 ` (No subject) William Kucharski
2021-12-28  1:36   ` Kefeng Wang
2008-01-03  8:33 Awad, Sinan (GE Healthcare)
2008-01-03 10:34 ` (no subject) Misbah khan
2006-07-06 12:21 Jochen Maes
     [not found] <20051227010004.D4C7568950@ozlabs.org>
2005-12-27 15:29 ` siman
2005-12-03 18:40 Otavio Salvador
2005-10-03  1:00 Bob Brose
2005-10-03  7:07 ` Andreas Schwab
2005-09-27 13:53 ÏÄÓê 
2005-09-27 16:07 ` Wolfgang Denk
2005-06-29  6:21 董晓凡
2005-06-29 16:22 ` evilninja
2005-06-27 12:25 FLAMENT David
2005-06-13 11:38 colui77
2005-02-13 12:28 Support for Adder875 in Linux 2.4 Markus Westergren
2005-02-14  6:45 ` Yuli Barcohen
2005-02-14 19:44   ` Markus Westergren
2005-02-15  9:35     ` (no subject) Yuli Barcohen
2004-11-22 19:23 Ratin Kumar
2004-11-22 22:53 ` Kumar Gala

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=6.2.1.2.1.20050412143653.02ae7720@mail.int.acdstar.com \
    --to=ejohnson@acdstar.com \
    --cc=linuxppc-embedded@ozlabs.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).