From: zql@glomationinc.com (Zhong Li)
To: linux-arm-kernel@lists.infradead.org
Subject: [alsa-devel] Bug? Sound support for at91sam9x5-wm8731 based boards
Date: Wed, 20 Nov 2013 12:41:13 -0500 [thread overview]
Message-ID: <045e01cee617$b53cf3b0$1fb6db10$@com> (raw)
In-Reply-To: <CACQ1gAh7UAkT1s_=gOKpzEt5bm9FAGf0gL-yM6=r5ch7bMksBA@mail.gmail.com>
>
> After reading the sources (mainly sound/soc/atmel/atmel_ssc_dai.c), I
> don't understand how the right and left channel are synchronized.
> (which one will be on TF rising edge, and which one on TF falling edge
> ?)
> In the SSC_TCMR register, the start event is TF_FALLING when there only
> one channel (i.e. mono source always on left channel) With a stereo
> source, it's TF_EDGE (Detection of any edge on TF
> signal) ; so the samples are transferred on rising and falling edge.
> I didn't see anything in the SSC what could synchronize the first
> sample with a TF falling edge.
> Or I missed something ?
>
The codec seems to be set to I2S mode based on the parameter name. And the FSOS field in the TFMR is set to be negative pulse. So it matches the I2S mode diagram (Figure 27 of WM8731 datasheet). The high to low on DACLRC (TF line aka PA25 pin) indicate start of the left channel data. Looks like the TF signal is automatically generated by the SSC controller according to the TFMR settings.
next prev parent reply other threads:[~2013-11-20 17:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 16:31 [PATCH 0/2] Remove some dead code for omaps Tony Lindgren
2013-11-19 16:31 ` [PATCH 1/2] ARM: OMAP2+: Remove legacy mux code for display.c Tony Lindgren
2013-11-19 16:31 ` [PATCH 2/2] ARM: OMAP2+: Remove legacy omap4_twl6030_hsmmc_init Tony Lindgren
[not found] ` <031f01cee547$950b5670$bf220350$@com>
2013-11-19 17:15 ` [alsa-devel] Bug? Sound support for at91sam9x5-wm8731 based boards Richard Genoud
2013-11-19 18:09 ` Zhong Li
2013-11-20 10:22 ` Richard Genoud
2013-11-20 16:23 ` Richard Genoud
2013-11-20 17:41 ` Zhong Li [this message]
2013-11-21 9:51 ` Richard Genoud
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='045e01cee617$b53cf3b0$1fb6db10$@com' \
--to=zql@glomationinc.com \
--cc=linux-arm-kernel@lists.infradead.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).