From: Peter Ujfalusi <peter.ujfalusi@nokia.com>
To: alsa-devel@alsa-project.org
Cc: broonie@opensource.wolfsonmicro.com, lrg@slimlogic.co.uk
Subject: [PATCH 0/2] ASoC: tlv320dac33 fixes
Date: Thu, 11 Mar 2010 16:26:20 +0200 [thread overview]
Message-ID: <1268317582-10284-1-git-send-email-peter.ujfalusi@nokia.com> (raw)
Hello,
Revisiting the start/stop sequence used by the tlv320dac33 codec in
order to avoid race conditions, which can occur, when the codec is in
FIFO modes.
It has been found that OMAP3 McBSP needs the BCLK continuously running
on the serial interface when it is configured to be slave.
DAC33 can be configured in a way, that it keeps the BCLK ticking, and
only enable the FS when it is needed.
Option for the platform data to select between continuous BCLK or non
continuous BCLK.
---
Peter Ujfalusi (2):
ASoC: tlv320dac33: Start/stop sequence change
ASoC: tlv320dac33: Add option for keeping the BCLK running
include/sound/tlv320dac33-plat.h | 1 +
sound/soc/codecs/tlv320dac33.c | 38 ++++++++++++++------------------------
2 files changed, 15 insertions(+), 24 deletions(-)
next reply other threads:[~2010-03-11 14:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 14:26 Peter Ujfalusi [this message]
2010-03-11 14:26 ` [PATCH 1/2] ASoC: tlv320dac33: Start/stop sequence change Peter Ujfalusi
2010-03-12 8:10 ` Liam Girdwood
2010-03-11 14:26 ` [PATCH 2/2] ASoC: tlv320dac33: Add option for keeping the BCLK running Peter Ujfalusi
2010-03-12 8:10 ` Liam Girdwood
2010-03-11 14:46 ` [PATCH 0/2] ASoC: tlv320dac33 fixes Jarkko Nikula
2010-03-11 14:55 ` Peter Ujfalusi
2010-03-11 15:07 ` Jarkko Nikula
2010-03-12 11:18 ` 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=1268317582-10284-1-git-send-email-peter.ujfalusi@nokia.com \
--to=peter.ujfalusi@nokia.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@slimlogic.co.uk \
/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).