From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@slimlogic.co.uk>
Subject: ASoC updates for 2.6.38
Date: Thu, 10 Mar 2011 14:20:35 +0000 [thread overview]
Message-ID: <20110310142035.GA18973@opensource.wolfsonmicro.com> (raw)
The following changes since commit ffd6eae2a0d18ca4a741615292a9c9ce904307fb:
ASoC: AM3517: Update codec name after multi-component update (2011-03-09 11:48:55 +0000)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound-2.6.git for-2.6.38
Mark Brown (4):
ASoC: Fix broken bitfield definitions in WM8978
ASoC: Use the correct DAPM context when cleaning up final widget set
ASoC: Fix typo in late revision WM8994 DAC2R name
ASoC: Ensure WM8958 gets all WM8994 late revision widgets
The DAPM context fix is essential for multi-component DAPM, without it
we will try to apply updates from the end of DAPM sequences to the wrong
device which isn't terribly clever. On other systems the change will be
a noop.
The other three updates are device specific ones, the WM8994/58 ones are
slightly more invasive but are critical to WM8958.
There may be one more update (for mini2440) coming later.
sound/soc/codecs/wm8978.c | 14 ++++++++------
sound/soc/codecs/wm8994.c | 10 +++++++++-
sound/soc/soc-dapm.c | 2 +-
3 files changed, 18 insertions(+), 8 deletions(-)
next reply other threads:[~2011-03-10 14:20 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 14:20 Mark Brown [this message]
2011-03-10 15:45 ` ASoC updates for 2.6.38 Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2011-03-02 11:34 Mark Brown
2011-03-02 14:48 ` Takashi Iwai
2011-02-25 11:51 Mark Brown
2011-02-25 11:59 ` Takashi Iwai
2011-02-18 4:19 Mark Brown
2011-02-22 4:49 ` Mark Brown
2011-02-22 7:24 ` Takashi Iwai
2011-02-08 11:34 Mark Brown
2011-02-08 16:31 ` Takashi Iwai
2011-02-01 14:56 Mark Brown
2011-02-01 21:25 ` Takashi Iwai
2011-01-26 11:34 Mark Brown
2011-01-26 13:40 ` Takashi Iwai
2011-01-24 15:17 Mark Brown
2011-01-24 16:44 ` Takashi Iwai
2011-01-19 10:22 Mark Brown
2011-01-19 11:29 ` Takashi Iwai
2011-01-19 11:35 ` Mark Brown
2011-01-18 13:03 Mark Brown
2011-01-18 13:06 ` Takashi Iwai
2011-01-12 11:17 Mark Brown
2011-01-12 11:44 ` Takashi Iwai
2011-01-05 12:50 Mark Brown
2011-01-08 12:06 ` Takashi Iwai
2010-12-27 17:51 Mark Brown
2010-12-27 17:43 Mark Brown
2010-12-23 12:05 Mark Brown
2010-12-23 14:11 ` Takashi Iwai
2010-12-22 11:03 Mark Brown
2010-12-22 11:59 ` Takashi Iwai
2010-12-14 18:38 Mark Brown
2010-12-14 19:05 ` Takashi Iwai
2010-12-09 16:17 Mark Brown
2010-12-09 17:21 ` Takashi Iwai
2010-12-06 14:35 Mark Brown
2010-12-06 14:39 ` Takashi Iwai
2010-12-03 17:46 Mark Brown
2010-12-04 7:59 ` Takashi Iwai
2010-11-29 19:08 Mark Brown
2010-11-30 7:21 ` Takashi Iwai
2010-11-24 13:16 Mark Brown
2010-11-24 13:41 ` Takashi Iwai
2010-11-22 11:14 Mark Brown
2010-11-22 12:16 ` Takashi Iwai
2010-11-02 14:54 Mark Brown
2010-11-02 15:17 ` 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=20110310142035.GA18973@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).