From: Roberto Fichera <kernel@tekno-soft.it>
To: Nicolin Chen <nicoleotsuka@gmail.com>
Cc: Fabio Estevam <fabio.estevam@freescale.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Shengjiu Wang <shengjiu.wang@freescale.com>,
Caleb Crome <caleb@crome.org>,
"arnaud.mouiche@invoxia.com" <arnaud.mouiche@invoxia.com>,
Markus Pargmann <mpa@pengutronix.de>,
"shawn.guo@linaro.org" <shawn.guo@linaro.org>,
Fabio Estevam <festevam@gmail.com>
Subject: Re: fsl_ssi.c: Roberto's problem: ssi hangs after some number of samples
Date: Wed, 4 Nov 2015 22:47:05 +0100 [thread overview]
Message-ID: <563A7CD9.6030804@tekno-soft.it> (raw)
In-Reply-To: <20151104181144.GA4057@Asurada-CZ80>
On 11/04/2015 07:11 PM, Nicolin Chen wrote:
> On Wed, Nov 04, 2015 at 06:52:12PM +0100, Roberto Fichera wrote:
>
>>> I notice your DMA buffer length is very short, which would require
>>> very frequency interrupts to service, right? Can you increase your
>>> DMA buffer length by increasing the period size? Maybe that would
>>> help reduce the likelyhood of a failure.
>> Not sure if this can help! SSI TDM is set to 32 slots but only 2 are masked. So every frame only
>> 2 slots are pushed/pulled from the FIFOs. maxburst is set to pull a block of 8 elements from the
>> FIFOs, DMA cyclic call it period. So the full DMA buffer is filled in buffer size / period DMA iterations.
> A smaller period size may course DMA buffer over/underrun -- ALSA
> over/underrun even though it seems that you didn't report any.
>
> And apparently SDMA would get more interrupt/callbacks. I would
> suggest a larger period size and buffer size although I cannot
> tie your problem with the size. But you may try.
Do you mean something like 2KB buffer and a period of 64 or 128 frames?
SDMA is supposed to wait the FIFO capacity
to complete a period, right?
next prev parent reply other threads:[~2015-11-04 21:47 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 18:01 fsl_ssi.c: Roberto's problem: ssi hangs after some number of samples Caleb Crome
2015-10-31 9:16 ` Roberto Fichera
2015-11-01 20:31 ` Fabio Estevam
2015-11-02 9:57 ` Roberto Fichera
2015-11-02 17:51 ` Roberto Fichera
2015-11-02 18:03 ` Roberto Fichera
2015-11-03 0:56 ` Caleb Crome
2015-11-03 8:21 ` Roberto Fichera
2015-11-03 21:26 ` Caleb Crome
2015-11-04 15:33 ` Roberto Fichera
2015-11-04 16:53 ` Roberto Fichera
2015-11-04 17:41 ` Caleb Crome
2015-11-04 17:52 ` Roberto Fichera
2015-11-04 18:11 ` Nicolin Chen
2015-11-04 21:47 ` Roberto Fichera [this message]
2015-11-05 10:03 ` Roberto Fichera
2015-11-05 11:30 ` Fabio Estevam
2015-11-05 11:48 ` Roberto Fichera
2015-11-04 17:58 ` Nicolin Chen
2015-11-04 18:09 ` Roberto Fichera
2015-11-04 18:18 ` Nicolin Chen
2015-11-04 21:48 ` Roberto Fichera
-- strict thread matches above, loose matches on Subject: below --
2015-11-05 21:34 Caleb Crome
2015-11-05 22:08 ` Roberto Fichera
2015-11-05 22:25 ` Caleb Crome
2015-11-05 22:40 ` Roberto Fichera
2015-11-05 22:49 ` Caleb Crome
2015-11-05 23:01 ` Roberto Fichera
2015-11-05 23:21 ` Caleb Crome
2015-11-05 23:28 ` Roberto Fichera
2015-11-05 23:30 ` Caleb Crome
2015-11-05 23:46 ` Roberto Fichera
2015-11-06 0:35 ` Caleb Crome
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=563A7CD9.6030804@tekno-soft.it \
--to=kernel@tekno-soft.it \
--cc=alsa-devel@alsa-project.org \
--cc=arnaud.mouiche@invoxia.com \
--cc=caleb@crome.org \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.com \
--cc=mpa@pengutronix.de \
--cc=nicoleotsuka@gmail.com \
--cc=shawn.guo@linaro.org \
--cc=shengjiu.wang@freescale.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