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 2/2] ASoC: tlv320dac33: Add option for keeping the BCLK running
Date: Fri, 12 Mar 2010 08:10:43 +0000 [thread overview]
Message-ID: <1268381443.3755.6.camel@odin> (raw)
In-Reply-To: <1268317582-10284-3-git-send-email-peter.ujfalusi@nokia.com>
On Thu, 2010-03-11 at 16:26 +0200, Peter Ujfalusi wrote:
> Platform data option for the codec to keep the BCLK clock
> continuously running in FIFO modes (codec master).
>
> OMAP3 McBSP when in slave mode needs continuous BCLK running
> on the serial bus in order to operate correctly.
>
> Since in FIFO mode the DAC33 can also shut down the BCLK clock
> and enable it only when it is needed, let the platforms decide
> if the CPU side needs the BCLK running or not.
>
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@nokia.com>
Acked-by: Liam Girdwood <lrg@slimlogic.co.uk>
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
next prev parent reply other threads:[~2010-03-12 8:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 14:26 [PATCH 0/2] ASoC: tlv320dac33 fixes Peter Ujfalusi
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 [this message]
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=1268381443.3755.6.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;
as well as URLs for NNTP newsgroup(s).