From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Takasi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@slimlogic.co.uk>
Subject: ASoC updates for 2.6.34
Date: Thu, 25 Feb 2010 16:10:00 +0000 [thread overview]
Message-ID: <20100225160959.GA3241@opensource.wolfsonmicro.com> (raw)
The following changes since commit d62abe563fa4718e7f85f3e871655434db92366d:
Misael Lopez Cruz (1):
OMAP4: PMIC: Add support for twl6030 codec
are available in the git repository at:
git://opensource.wolfsonmicro.com/linux-2.6-asoc.git for-2.6.34
These wind up being a bug fix, without fixing the reporting of the
periods a lot of hardware is going to get lots of clock domain issues.
Mark Brown (2):
ASoC: Remove a unused variables from i.MX FIQ runtime data
ASoC: Check progress when reporting periods from i.MX FIQ handler
sound/soc/imx/imx-pcm-fiq.c | 40 ++++++++++++++++++++++++++++++----------
1 files changed, 30 insertions(+), 10 deletions(-)
next reply other threads:[~2010-02-25 16:09 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 16:10 Mark Brown [this message]
2010-02-25 16:37 ` ASoC updates for 2.6.34 Takashi Iwai
2010-02-25 17:44 ` Mark Brown
2010-02-25 18:45 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2010-04-16 2:23 Mark Brown
2010-04-16 8:06 ` Takashi Iwai
2010-04-12 15:33 Mark Brown
2010-04-08 15:11 Mark Brown
2010-04-08 15:55 ` Mark Brown
2010-04-13 8:20 ` Takashi Iwai
2010-04-13 8:29 ` Mark Brown
2010-04-13 14:38 ` Sascha Hauer
2010-04-05 18:38 Mark Brown
2010-04-05 19:29 ` Takashi Iwai
2010-04-12 11:31 ` Daniel Mack
2010-04-13 8:34 ` Mark Brown
2010-03-29 20:10 Mark Brown
2010-03-30 6:08 ` Takashi Iwai
2010-03-22 16:46 Mark Brown
2010-03-22 17:11 ` Takashi Iwai
2010-03-19 14:31 Mark Brown
2010-03-19 20:34 ` Takashi Iwai
2010-03-03 20:14 Mark Brown
2010-03-03 21:51 ` Takashi Iwai
2010-02-23 19:48 Mark Brown
2010-02-23 20:01 ` Takashi Iwai
2010-02-17 16:29 Mark Brown
2010-02-17 20:34 ` Takashi Iwai
2010-02-16 19:20 Mark Brown
2010-02-16 20:01 ` Takashi Iwai
2010-02-12 16:27 Mark Brown
2010-02-10 11:35 Mark Brown
2010-02-10 19:40 ` Takashi Iwai
2010-02-05 17:21 Mark Brown
2010-02-05 19:24 ` Takashi Iwai
2010-02-04 12:40 Mark Brown
2010-02-04 13:22 ` Takashi Iwai
2010-02-02 13:51 Mark Brown
2010-02-02 14:37 ` Takashi Iwai
2010-02-01 19:00 Mark Brown
2010-02-01 23:27 ` Takashi Iwai
2010-01-28 15:51 Mark Brown
2010-01-28 16:17 ` Takashi Iwai
2010-01-27 23:16 Mark Brown
2010-01-27 23:30 ` Takashi Iwai
2010-01-25 18:47 Mark Brown
2010-01-26 7:14 ` Takashi Iwai
2010-01-21 12:42 Mark Brown
2010-01-21 13:30 ` Takashi Iwai
2010-01-17 17:24 Mark Brown
2010-01-18 7:14 ` Takashi Iwai
2010-01-12 13:20 Mark Brown
2010-01-12 13:27 ` Takashi Iwai
2010-01-12 13:35 ` Takashi Iwai
2010-01-12 13:40 ` Takashi Iwai
2010-01-12 13:42 ` Mark Brown
2010-01-12 13:45 ` Takashi Iwai
2010-01-12 14:08 ` Mark Brown
2010-01-12 14:14 ` Takashi Iwai
2010-01-12 14:19 ` Mark Brown
2010-01-12 14:21 ` Takashi Iwai
2010-01-25 8:21 ` Barry Song
2010-01-12 13:48 ` Takashi Iwai
2010-01-12 14:09 ` Mark Brown
2010-01-12 14:12 ` Peter Ujfalusi
2010-01-12 14:14 ` Mark Brown
2010-01-12 14:25 ` Peter Ujfalusi
2010-01-12 14:19 ` Takashi Iwai
2010-01-12 14:37 ` Mark Brown
2010-01-12 14:41 ` Takashi Iwai
2010-01-12 14:50 ` Mark Brown
2009-12-18 13:59 Mark Brown
2009-12-18 14:18 ` Takashi Iwai
2009-12-18 14:32 ` Mark Brown
2009-12-18 14:35 ` Takashi Iwai
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=20100225160959.GA3241@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@slimlogic.co.uk \
--cc=tiwai@suse.de \
/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).