alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Takaashi Iwai <twai@suse.de>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@slimlogic.co.uk>
Subject: ASoC updates for 2.6.38
Date: Thu, 17 Feb 2011 20:19:34 -0800	[thread overview]
Message-ID: <20110218041933.GB6069@opensource.wolfsonmicro.com> (raw)

The following changes since commit 6ed8f1485fc82d44ac464bc84a7dcdddd1fa096f:

  ASoC: Improve WM8994 digital power sequencing (2011-02-03 20:17:13 +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

These are all driver specific with the exception of the two commits from
me.  These are both small and focused changes which fix obvious issues
for some systems, both being things that the framework should clearly
have been doing but had omitted to do.

Dimitris Papastamos (2):
      ASoC: WM8994: Improve robustness in some use cases
      ASoC: WM8994: Improve playback robustness

Janusz Krzysztofik (1):
      ASoC: CX20442: fix wrong reg_cache_default content

Mark Brown (2):
      ASoC: Sync initial widget state with hardware
      ASoC: Ensure supplies are maintained for force enabled widgets

Stephen Warren (2):
      ASoC: WM8903: Fix mic detection register definitions
      ASoC: WM8903: Fix mic detection enable logic

 include/sound/wm8903.h     |   10 +--
 sound/soc/codecs/cx20442.c |    2 +-
 sound/soc/codecs/wm8903.c  |    2 +-
 sound/soc/codecs/wm8994.c  |  197 ++++++++++++++++++++++++++++++++++++++++---
 sound/soc/soc-dapm.c       |   23 +++++-
 5 files changed, 210 insertions(+), 24 deletions(-)

             reply	other threads:[~2011-02-18  4:19 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-18  4:19 Mark Brown [this message]
2011-02-22  4:49 ` ASoC updates for 2.6.38 Mark Brown
2011-02-22  7:24   ` Takashi Iwai
  -- strict thread matches above, loose matches on Subject: below --
2011-03-10 14:20 Mark Brown
2011-03-10 15:45 ` Takashi Iwai
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-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=20110218041933.GB6069@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=lrg@slimlogic.co.uk \
    --cc=twai@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).