From: Alex <lee188@singnet.com.sg>
To: alsa-devel@alsa-project.org
Subject: Re: SoC Atmel SSC stereo problem
Date: Sat, 23 Oct 2010 04:10:22 +0000 (UTC) [thread overview]
Message-ID: <loom.20101023T054800-433@post.gmane.org> (raw)
In-Reply-To: 4CC20475.3020900@fh-kl.de
Patrick Ziegler <patrick.ziegler <at> fh-kl.de> writes:
> The SSC is connected to a FPGA that assigns the bus to different devices
> depending on the application. And for all applications the FPGA
> generates the clocks. Maybe this is not the best solution but I will try
> to deal with this limitation first before I try to persuade other people
> to change it.
>
Hi Patrick,
It looks like you are running the SSC TX in slave mode, with both the SCLK (the
i2S clock) and LRCK provided by your FPGA. It is trickier to prevent channel
inversion in this mode.
One possible approach is to:
(1) test for the LRCK level with a gpio pin connected to the LRCK. This should
normally be the same pin assigned to TX_FRAME_SYNC. After any USB set interface
to the alternate setting for playback of your active device, or after any
sampling rate change etc., you re-sync the transfer to the correct LRCK edge:
pdca_disable(PDCA_CHANNEL_SSC_TX);
// reset the audio buffer pointers to the start of the LEFT channel etc
// if required
// re-sync SSC to LRCK
// Wait for the next frame synchronization event
// to avoid channel inversion. Start with left channel - FS goes low
while (!gpio_get_pin_value(_LRCK));
while (gpio_get_pin_value(LRCK));
// exit when FS goes low
// Enable now the transfer.
pdca_enable(PDCA_CHANNEL_SSC_TX);
(2) start clocking data out at any LRCK edge after a suitable delay (of 1
SCLK). You may need to use LRCK level change rather than any edge depending on
the hardware timing. The delay may also need to be adjusted depending on
hardware timing.
(3) clock out one sample (either left or right) per LRCK edge (or level).
Of course, if you are running the SSC in master mode, there are easier ways to
ensure channel synchronization :-)
The above suggestion is extrapolated from my project using the AT32UC3A3 which
has a similar (more capable) SSC as the AT91. So it may or may not work for
you.
Alex
next prev parent reply other threads:[~2010-10-23 4:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 15:17 SoC Atmel SSC stereo problem Patrick Ziegler
2010-10-22 16:11 ` Clemens Ladisch
2010-10-22 21:39 ` Patrick Ziegler
2010-10-23 4:10 ` Alex [this message]
2010-10-25 9:16 ` Patrick Ziegler
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=loom.20101023T054800-433@post.gmane.org \
--to=lee188@singnet.com.sg \
--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