All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Juergen Beisert <jbe@pengutronix.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: SoC sound support for imx27
Date: Mon, 5 May 2008 14:12:17 +0100	[thread overview]
Message-ID: <20080505131216.GA5217@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <200805051455.05277.jbe@pengutronix.de>

On Mon, May 05, 2008 at 02:55:04PM +0200, Juergen Beisert wrote:

> Hmm, how far away is ASoC v2 from mainline? When I start to develop the driver 
> right now, what version I should use?

Depends on how quickly you want to get it into the mainline.  Developing
for v1 would be the most conservative choice and let you get stuff in as
soon as possible without being held up by v2 but it would mean that
you'd be working with the ASoC v1 interfaces and that someone will have
to convert to v2 at some point.

The idea is that ASoC v2 itself should be starting to make its way into
mainline during 2.6.27 but there's no guarantees that it'll make it
then.

  reply	other threads:[~2008-05-05 13:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-23 14:54 SoC sound support for imx27 Juergen Beisert
2008-04-23 15:36 ` Liam Girdwood
2008-04-24 11:19   ` Juergen Beisert
2008-04-24 14:26     ` Liam Girdwood
2008-04-24 14:31       ` Timur Tabi
2008-04-24 14:11   ` Juergen Beisert
2008-04-24 14:30     ` Liam Girdwood
2008-05-05 10:56       ` Juergen Beisert
2008-05-05 12:42         ` Mark Brown
2008-05-05 12:55           ` Juergen Beisert
2008-05-05 13:12             ` Mark Brown [this message]
2008-05-08  7:54           ` Juergen Beisert
2008-05-08  9:33             ` Mark Brown
2008-05-08 10:27               ` How are events of headphone plug/unplug handled in ASOC Srinivas.Kandagatla
2008-05-08 10:31                 ` Mark Brown
2008-05-08 11:25             ` SoC sound support for imx27 Liam Girdwood
2008-04-23 15:44 ` Timur Tabi

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=20080505131216.GA5217@rakim.wolfsonmicro.main \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=jbe@pengutronix.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.