From: Juergen Beisert <jbe@pengutronix.de>
To: alsa-devel@alsa-project.org
Subject: Digital Audio Multiplexer of the i.MX27 processor
Date: Tue, 27 May 2008 17:13:49 +0200 [thread overview]
Message-ID: <200805271713.49868.jbe@pengutronix.de> (raw)
Hi,
does anybody understand the DAM unit in the i.MX27 processor?
This routing device drivers me crazy, as I do not understand how to route
clocks, syncs and the data signals of my internal i2s unit to the processor's
pins.
All I can see is, when I enable the internal SSI unit in i2s mode, the DMA
unit transfers some data into it, but the SSI unit does not shift it out. So
everything stops, the DMA timeouts and I cannot hear anything. I can see the
external device generates clock and frame signals, but it seems they do not
reach the internal SSI unit.
Has anybody a working DAM configuration which uses the internal SSI#1 as an
i2s slave, an external i2s device connected to the SSI#1 pin group of this
processor which acts as a master (I did not find anything in the manual, how
the relation between the internal so called port-1 to port-6 at the DAM unit
and the 4 external SSI1...SSI4 pin groups are). Means the external i2s device
generates the clock and frame signal and the internal SSI#1 unit in i2s mode
should use it to send serial sound data to the external device.
Juergen
--
Dipl.-Ing. Juergen Beisert | http://www.pengutronix.de
Pengutronix - Linux Solutions for Science and Industry
Handelsregister: Amtsgericht Hildesheim, HRA 2686
Vertretung Sued/Muenchen, Germany
Phone: +49-8766-939 228 | Fax: +49-5121-206917-9
next reply other threads:[~2008-05-27 15:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-27 15:13 Juergen Beisert [this message]
2008-05-27 23:03 ` Digital Audio Multiplexer of the i.MX27 processor Peter Wurmsdobler
2008-05-28 8:42 ` Juergen Beisert
2008-05-30 8:57 ` Aditya Shankar
2008-05-30 9:17 ` Juergen Beisert
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=200805271713.49868.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=alsa-devel@alsa-project.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