Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: ASoC updates for 2.6.31
Date: Thu, 16 Apr 2009 14:50:27 +0100	[thread overview]
Message-ID: <20090416135026.GA10878@rakim.wolfsonmicro.main> (raw)

The following changes since commit 6967963d6d5cac40a091d075326f0e3ccb95c58a:
  Mark Brown (1):
        Merge branch 'for-2.6.30' into for-2.6.31

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound-2.6.git for-2.6.31

Ben Dooks (4):
      ASoC: Fix jive_wm8750.c build problems
      ASoC: s3c-i2s-v2.c fix for s3c_i2sv2_iis_calc_rate
      ASoC: Fix s3c-i2s-v2.c snd_soc_dai changes
      ASoC: Fix include build error in s3c2412-i2s.c

Daniel Mack (1):
      ASoC: pxa-ssp: allow setting of dai format 0

Jarkko Nikula (2):
      ASoC: OMAP: Fix DSP_B format in OMAP McBSP DAI driver
      ASoC: OMAP: Fix FS polarity in OSK5912 machine driver

Mark Brown (4):
      ASoC: Check we have DAI ops when calling via accessor functions
      ASoC: Volume controls are never of boolean type
      ASoC: Request shared rates for WM8903
      Merge branch 'for-2.6.30' into for-2.6.31

Peter Ujfalusi (2):
      ASoC: OMAP: Use single-phase for DSP mode
      ASoC: OMAP: Add DSP_A mode support for mcbsp

 sound/soc/codecs/wm8903.c       |    1 +
 sound/soc/omap/omap-mcbsp.c     |   45 ++++++++++++++++++++++++++------------
 sound/soc/omap/osk5912.c        |    4 +-
 sound/soc/pxa/pxa-ssp.c         |    1 +
 sound/soc/s3c24xx/jive_wm8750.c |   12 +++++-----
 sound/soc/s3c24xx/s3c-i2s-v2.c  |   18 ++++++++-------
 sound/soc/s3c24xx/s3c2412-i2s.c |    2 +-
 sound/soc/soc-core.c            |   20 ++++++++--------
 8 files changed, 62 insertions(+), 41 deletions(-)

             reply	other threads:[~2009-04-16 13:50 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-16 13:50 Mark Brown [this message]
2009-04-16 14:06 ` ASoC updates for 2.6.31 Takashi Iwai
  -- strict thread matches above, loose matches on Subject: below --
2009-07-10 19:25 Mark Brown
2009-07-06 20:49 Mark Brown
2009-07-07  5:56 ` Takashi Iwai
2009-07-01 20:45 Mark Brown
2009-07-02  8:55 ` Takashi Iwai
2009-06-25 13:09 Mark Brown
2009-06-25 13:35 ` Takashi Iwai
2009-06-21 13:15 Mark Brown
2009-06-22  6:20 ` Takashi Iwai
2009-06-03 10:51 Mark Brown
2009-06-03 11:02 ` Takashi Iwai
2009-05-28 18:04 Mark Brown
2009-05-28 18:12 ` Takashi Iwai
2009-05-27 10:48 Mark Brown
2009-05-27 13:58 ` Takashi Iwai
2009-05-25 12:07 Mark Brown
2009-05-25 12:29 ` Takashi Iwai
2009-05-22 20:21 Mark Brown
2009-05-22 20:34 ` Takashi Iwai
2009-05-19 19:27 Mark Brown
2009-05-19 19:39 ` Takashi Iwai
2009-05-18 15:04 Mark Brown
2009-05-18 15:16 ` Takashi Iwai
2009-05-15  8:23 ASoC updates for 2.6.30 Mark Brown
2009-05-15  8:26 ` ASoC updates for 2.6.31 Mark Brown
2009-05-15  8:34   ` Takashi Iwai
2009-05-12 10:25 Mark Brown
2009-05-08 12:57 Mark Brown
2009-05-08 14:37 ` Takashi Iwai
2009-05-05 10:01 Mark Brown
2009-05-05 10:45 ` Takashi Iwai
2009-04-28 15:22 Mark Brown
2009-04-23 19:54 Mark Brown
2009-04-24  6:10 ` Takashi Iwai
2009-04-20 11:58 Mark Brown
2009-04-20 12:05 ` Takashi Iwai
2009-04-14 12:32 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=20090416135026.GA10878@rakim.wolfsonmicro.main \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --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