From: Lars-Peter Clausen <lars@metafoo.de>
To: Anatol Pomozov <anatol.pomozov@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: liam.r.girdwood@linux.intel.com, 陳立峰 <albertchen@realtek.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [PATCH] ASoC: Document DAI signal polarity
Date: Wed, 30 Sep 2015 21:34:46 +0200 [thread overview]
Message-ID: <560C3956.9000302@metafoo.de> (raw)
In-Reply-To: <CAOMFOmXX67Uktd4cVJ==1w-nfHzFF_HaKwVb+sqLMp4WPt0Knw@mail.gmail.com>
On 09/30/2015 09:08 PM, Anatol Pomozov wrote:
> - for I2S/left/right justified - frame starts with falling FSYNC edge
This is what most drivers implement:
I2S: Left channel starts with the falling edge, right channel starts with
the rising edge (data is delayed by one clock cycle)
Right/Left justified: Left channel starts with the rising edge, right
channel starts with the falling edge
DSP A/B: Frame starts with the rising edge. Channels are spaced by the
configured slot width (e.g. first channel at offset 0, second channel at
offset 16, third channel at offset 32, ...). If the slot with has not been
configured explicitly using the set_tdm_slots() API the slot with is the
number of bits in one single-channel sample (Return value of params_width()).
When using I2S or left/right justified in TDM mode channels are also spaced
by the configured slot width and the second edge should be ignored.
next prev parent reply other threads:[~2015-09-30 19:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 20:50 [PATCH] ASoC: Document DAI signal polarity Anatol Pomozov
2015-09-01 1:27 ` Albert Chen
2015-09-01 7:20 ` arnaud.mouiche
2015-09-18 13:54 ` Mark Brown
2015-09-29 21:34 ` Anatol Pomozov
2015-09-30 18:10 ` Mark Brown
2015-09-30 19:08 ` Anatol Pomozov
2015-09-30 19:22 ` Benoît Thébaudeau
2015-09-30 22:33 ` Mark Brown
2015-09-30 19:28 ` Mark Brown
2015-09-30 19:34 ` Lars-Peter Clausen [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-10-01 18:09 Anatol Pomozov
2015-10-01 19:18 ` Benoît Thébaudeau
2015-10-05 15:12 ` Mark Brown
2015-10-05 19:20 ` Benoît Thébaudeau
2015-10-06 9:33 ` Mark Brown
2015-10-02 15:33 Anatol Pomozov
2015-10-02 17:01 ` Benoît Thébaudeau
2015-10-08 16:37 Anatol Pomozov
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=560C3956.9000302@metafoo.de \
--to=lars@metafoo.de \
--cc=albertchen@realtek.com \
--cc=alsa-devel@alsa-project.org \
--cc=anatol.pomozov@gmail.com \
--cc=broonie@kernel.org \
--cc=liam.r.girdwood@linux.intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.