From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Peter Ujfalusi <peter.ujfalusi@nokia.com>
Cc: alsa-devel@alsa-project.org, broonie@opensource.wolfsonmicro.com
Subject: Re: [PATCH 1/5] ASoC: tlv320dac33: Fix for early interrupt in FIFO Mode1
Date: Thu, 22 Apr 2010 17:26:51 +0100 [thread overview]
Message-ID: <1271953611.3228.435.camel@odin> (raw)
In-Reply-To: <1271944670-14588-2-git-send-email-peter.ujfalusi@nokia.com>
On Thu, 2010-04-22 at 16:57 +0300, Peter Ujfalusi wrote:
> Alarm threshold interrupt is triggered right after the
> playback start.
> This interrupt is recieved during the first burst period,
> and caused the state machine to write additional nSample
> command, which has to be avoided.
> To fix this issue move the DAC33 interrupt unmasking
> after we configured the PREFILL register with a small
> delay.
>
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@nokia.com>
> ---
> sound/soc/codecs/tlv320dac33.c | 6 ++++--
> 1 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/sound/soc/codecs/tlv320dac33.c b/sound/soc/codecs/tlv320dac33.c
> index 824bb35..8a7265f 100644
> --- a/sound/soc/codecs/tlv320dac33.c
> +++ b/sound/soc/codecs/tlv320dac33.c
> @@ -557,9 +557,12 @@ static inline void dac33_prefill_handler(struct tlv320dac33_priv *dac33)
> switch (dac33->fifo_mode) {
> case DAC33_FIFO_MODE1:
> dac33_write16(codec, DAC33_NSAMPLE_MSB,
> - DAC33_THRREG(dac33->nsample));
> + DAC33_THRREG(dac33->nsample + dac33->alarm_threshold));
> dac33_write16(codec, DAC33_PREFILL_MSB,
> DAC33_THRREG(dac33->alarm_threshold));
> + /* Enable Alarm Threshold IRQ */
> + msleep(2);
Does this sleep depend on rate/frame_size in any way ?
Liam
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
next prev parent reply other threads:[~2010-04-22 16:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 13:57 [PATCH 0/5] ASoC: tlv320dac33: FIFO caused delay reporting and fixes Peter Ujfalusi
2010-04-22 13:57 ` [PATCH 1/5] ASoC: tlv320dac33: Fix for early interrupt in FIFO Mode1 Peter Ujfalusi
2010-04-22 16:26 ` Liam Girdwood [this message]
2010-04-23 5:33 ` Peter Ujfalusi
2010-04-22 13:57 ` [PATCH 2/5] ASoC: tlv320dac33: Skip calculations in FIFO Bypass mode Peter Ujfalusi
2010-04-22 13:57 ` [PATCH 3/5] ASoC: tlv320dac33: Change magic numbers used in Mode7 Peter Ujfalusi
2010-04-22 13:57 ` [PATCH 4/5] ASoC: tlv320dac33: Calculate the interface speed during bursts Peter Ujfalusi
2010-04-22 13:57 ` [PATCH 5/5] ASoC: tlv320dac33: FIFO caused delay reporting Peter Ujfalusi
2010-04-22 17:57 ` Liam Girdwood
2010-04-23 5:52 ` 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=1271953611.3228.435.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=peter.ujfalusi@nokia.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