From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Leonardo Gabrielli <l.gabrielli@univpm.it>
Cc: alsa-devel@alsa-project.org
Subject: Re: twl4030 latency update
Date: Wed, 26 Mar 2014 10:41:07 +0200 [thread overview]
Message-ID: <533292A3.5070000@ti.com> (raw)
In-Reply-To: <53328F4C.8030205@ti.com>
On 03/26/2014 10:26 AM, Peter Ujfalusi wrote:
> Hi Leonardo,
>
> On 03/25/2014 08:50 PM, Leonardo Gabrielli wrote:
>> Thanks Peter,
>> I've been able today to test following your suggestions.
>> Unfortunately I didn't get any improvement on latency, but reducing sDMA FIFO
>> threshold improved on audio integrity (with some period+samplerate
>> combinations I have corrupted audio, maybe scrambled or empty frames).
>
> Can you elaborate on the corrupted/scrambled audio? I just don't see how it
> can happen. Can you get the /proc/asound/card0/pcm0p/sub0/hw_params when you
> have the audio quality issue?
>
> I can not run jackd on the board anymore (with linux-next at least):
> FATAL: cannot locate cpu MHz in /proc/cpuinfo
>
> but with aplay -v --period-size=512 or 64 2ch-left-since-22050.wav
> seams to be fine for me (assuming AU=ko means that it is the corrupted one)
Yeah, this is not correct. it means 512 or 64 periods and not the period sizes.
I would need the hw_params for the actual playback to be able to reproduce the
issue.
--
Péter
next prev parent reply other threads:[~2014-03-26 8:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-20 11:13 twl4030 latency update Leonardo Gabrielli
2014-03-20 13:35 ` Peter Ujfalusi
2014-03-20 14:31 ` Leonardo Gabrielli
2014-03-21 7:08 ` Peter Ujfalusi
2014-03-25 18:50 ` Leonardo Gabrielli
2014-03-26 8:26 ` Peter Ujfalusi
2014-03-26 8:41 ` Peter Ujfalusi [this message]
2014-03-26 9:35 ` Leonardo Gabrielli
2014-03-26 12:28 ` Peter Ujfalusi
2014-03-26 9:45 ` Leonardo Gabrielli
2014-03-26 12:51 ` Peter Ujfalusi
2014-03-26 15:40 ` Leonardo Gabrielli
[not found] ` <533A89D2.5050906@univpm.it>
2014-04-01 13:31 ` Peter Ujfalusi
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=533292A3.5070000@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=l.gabrielli@univpm.it \
/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