From: Nicolin Chen <nicoleotsuka@gmail.com>
To: Alexander Shiyan <shc_work@mail.ru>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>,
Xiubo Li <Xiubo.Lee@gmail.com>, Timur Tabi <timur@tabi.org>,
Takashi Iwai <tiwai@suse.com>, Mark Brown <broonie@kernel.org>,
Fabio Estevam <fabio.estevam@nxp.com>
Subject: Re: [PATCH 2/2] ASoC: fsl_ssi: Fix number of words per frame for I2S-slave mode
Date: Wed, 29 Jun 2016 11:26:10 -0700 [thread overview]
Message-ID: <20160629182609.GA17986@Asurada-Nvidia> (raw)
In-Reply-To: <1467186721.688218396@f75.i.mail.ru>
On Wed, Jun 29, 2016 at 10:52:01AM +0300, Alexander Shiyan wrote:
> >your failed case. Could you please tell me what were the FSclk,
> >BITclk and size of your case?
> Here is my oscillograms with/without patch:
> Bclk=12 MHz, sound is just a "cat /dev/urandom > /dev/dsp", i.e. FS=8 KHz, MONO.
> Upper (yellow) line is TXDATA, Lower (blue) is FS.
>
> Measurement without patch: https://cloud.mail.ru/public/Rcsv/xr88V5Sa1
> Measurement with patch: https://cloud.mail.ru/public/NCwn/DQnzioQEL
Thanks for the reply. So in the case without patch, it looks like
SSI just sent the data ignoring the slot size right?
next prev parent reply other threads:[~2016-06-29 18:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-25 4:59 [PATCH 2/2] ASoC: fsl_ssi: Fix number of words per frame for I2S-slave mode Alexander Shiyan
2016-06-28 18:20 ` Nicolin Chen
[not found] ` <1467143972.433375523@f318.i.mail.ru>
2016-06-28 22:06 ` Nicolin Chen
2016-06-29 7:52 ` Alexander Shiyan
2016-06-29 18:26 ` Nicolin Chen [this message]
[not found] ` <1467226224.156244316@f360.i.mail.ru>
2016-06-29 20:56 ` Nicolin Chen
2016-06-28 22:02 ` Nicolin Chen
2016-06-29 18:20 ` Applied "ASoC: fsl_ssi: Fix number of words per frame for I2S-slave mode" to the asoc tree Mark Brown
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=20160629182609.GA17986@Asurada-Nvidia \
--to=nicoleotsuka@gmail.com \
--cc=Xiubo.Lee@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=lgirdwood@gmail.com \
--cc=shc_work@mail.ru \
--cc=timur@tabi.org \
--cc=tiwai@suse.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 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).