alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Nikula <jhnikula@gmail.com>
To: Liam Girdwood <lrg@slimlogic.co.uk>
Cc: vbarinov <vbarinov@embeddedalley.com>,
	alsa-devel <alsa-devel@alsa-project.org>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Wan ZongShun <mcuos.com@gmail.com>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	jassisinghbrar <jassisinghbrar@gmail.com>,
	Peter Ujfalusi <peter.ujfalusi@nokia.com>,
	Cliff Cai <cliff.cai@analog.com>,
	Zhuang <haojian.zhuang@gmail.com>,
	Sedji Gaouaou <sedji.gaouaou@atmel.com>,
	"timur.tabi@gmail.com" <timur.tabi@gmail.com>,
	Lars-Peter Clausen <lars@metafoo.de>,
	"Candelaria Villareal,  Jorge" <jorge.candelaria@ti.com>,
	"vaibhav.bedia" <vaibhav.bedia@ti.com>,
	Kuninori Morimoto <morimoto.kuninori@renesas.com>,
	Haojian@alsa-project.org, Ryan Mallon <ryan@bluewatersys.com>
Subject: Re: [RFC 0/5] ASoC multi-component support : core
Date: Mon, 28 Jun 2010 10:16:21 +0300	[thread overview]
Message-ID: <20100628101621.c811a1da.jhnikula@gmail.com> (raw)
In-Reply-To: <1277407467.3100.579.camel@odin>

On Thu, 24 Jun 2010 20:24:27 +0100
Liam Girdwood <lrg@slimlogic.co.uk> wrote:

> I've so far tested the new multi-component enumeration on the TI OMAP
> and Marvell PXA platforms with AC97, MFD and I2C based CODECs. I do
> however need ASoC platform maintainers to test on their systems (as I
> only have a subset of the hardware). Some ASOC platforms do need a
> little extra checking/fixups too :- 
> 
I wouldn't expect much problems from OMAPs. Beagle with TWL4030 works
out of box and I would expect other boards using TWL4030 to work as
well.

If some board doesn't work then fix is most probably just
adding .codec_id = I2C address of the codec (or -1) to snd_soc_dai_link
structure of that machine.


-- 
Jarkko

  parent reply	other threads:[~2010-06-28  7:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-24 19:24 [RFC 0/5] ASoC multi-component support : core Liam Girdwood
2010-06-24 21:36 ` Ryan Mallon
2010-06-24 23:12   ` Mark Brown
2010-06-24 23:38     ` Ryan Mallon
2010-06-25  4:51       ` Ryan Mallon
2010-06-25  8:37         ` Liam Girdwood
2010-06-25 22:38           ` Ryan Mallon
2010-06-26 17:52             ` Liam Girdwood
2010-06-26  2:25 ` Wan ZongShun
2010-06-26 17:29   ` Liam Girdwood
2010-06-28  7:16 ` Jarkko Nikula [this message]
2010-07-01 19:35   ` Mark Brown
2010-07-01 19:55 ` [PATCH] ASoC: Use bool rather than 1 bit bitfield in multi-component Mark Brown
2010-07-05 21:10   ` Liam Girdwood
2010-07-01 20:01 ` [RFC 0/5] ASoC multi-component support : core 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=20100628101621.c811a1da.jhnikula@gmail.com \
    --to=jhnikula@gmail.com \
    --cc=Haojian@alsa-project.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=cliff.cai@analog.com \
    --cc=haojian.zhuang@gmail.com \
    --cc=jassisinghbrar@gmail.com \
    --cc=jorge.candelaria@ti.com \
    --cc=lars@metafoo.de \
    --cc=lrg@slimlogic.co.uk \
    --cc=mcuos.com@gmail.com \
    --cc=morimoto.kuninori@renesas.com \
    --cc=peter.ujfalusi@nokia.com \
    --cc=ryan@bluewatersys.com \
    --cc=s.hauer@pengutronix.de \
    --cc=sedji.gaouaou@atmel.com \
    --cc=timur.tabi@gmail.com \
    --cc=vaibhav.bedia@ti.com \
    --cc=vbarinov@embeddedalley.com \
    /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).