All of 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, Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: Missing patches for 2.6.38 merge?
Date: Tue, 11 Jan 2011 22:17:49 +0000	[thread overview]
Message-ID: <20110111221749.GA28212@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <s5hipxvi6rm.wl%tiwai@suse.de>

On Tue, Jan 11, 2011 at 08:23:41PM +0100, Takashi Iwai wrote:

> Mark, Liam, do you guys have still many pending updates?  If so, please
> forward quickly.  Also, if a brief summary of this merge in ASoC area
> is ready, it'd be helpful.

Big update...

 - Enhancements to multi-component from Jarkko Nikula allowing multiple
   devices of the same type to be included in one system (and handling
   other overlaps between devices) and support cross device DAPM. 

 - Support from Dimitris Papastamos for compressing the register cache in
   memory using either an rbtree or LZO, giving substantial memory savings
   on CODECs with large register maps.

 - Addition of trace points around DAPM and register I/O operation,
   allowing very low overhead logging without interfering with the main
   system log, useful for collecting verbose diagnostics without
   interfering with system operation and for always enabled flight recorder
   style tracking for intermittent problems.

 - Restructuring of the Samsung CPU support from Jassi Brar, including a
   number of really good usability improvements.

 - New CODEC drivers for ALC5621/2/3, WM8737, WM8770 and WM8958.

 - Machine support for HP iPAQ H1940, HP t5325 thin clients and OpenRC
   Ultimate.

  reply	other threads:[~2011-01-11 22:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11 19:23 Missing patches for 2.6.38 merge? Takashi Iwai
2011-01-11 22:17 ` Mark Brown [this message]
2011-01-12  1:04   ` Liam Girdwood
2011-01-12  7:49 ` Clemens Ladisch
2011-01-12  7:50   ` 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=20110111221749.GA28212@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.