From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter Ujfalusi <peter.ujfalusi@nokia.com>
Cc: alsa-devel@alsa-project.org,
"Valkeinen Tomi (Nokia-D/Helsinki)" <Tomi.Valkeinen@nokia.com>,
Thomas Weber <swirl@gmx.li>,
"weber@corscience.de" <weber@corscience.de>,
"tony@atomride.com" <tony@atomride.com>,
"Balbi Felipe (Nokia-D/Helsinki)" <felipe.balbi@nokia.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [alsa-devel] [PATCHv3 3/4] Add ASoC support for DevKit8000
Date: Thu, 11 Feb 2010 16:42:28 +0000 [thread overview]
Message-ID: <20100211164227.GA18464@sirena.org.uk> (raw)
In-Reply-To: <201002111702.54783.peter.ujfalusi@nokia.com>
On Thu, Feb 11, 2010 at 05:02:54PM +0200, Peter Ujfalusi wrote:
> On Thursday 11 February 2010 13:14:18 ext Jarkko Nikula wrote:
> > Yeah, after thinking twice, we don't have zillions of options for e.g.
> > Intel HDA either. If we ever figure out some common OMAP+TWL4030
> Well, I really doubt that we can find a way to have a common driver for this
> combination. You can attach quite a big variety of amps to the outputs (some
> controlled with GPIO, some like the tpa6130 has i2c interface, etc).
> To have some kind of "infrastructure" to support all of the possible scenarios
> is just does not worth the effort IMHO.
On the other hand there's probably going to be a bunch of boards which
can use the same driver by virtue of having copied the audio subsystem
en masse from one of the reference designs.
prev parent reply other threads:[~2010-02-11 16:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 19:23 [PATCHv3 3/4] Add ASoC support for DevKit8000 Thomas Weber
2010-02-11 9:55 ` Liam Girdwood
2010-02-11 10:40 ` Jarkko Nikula
2010-02-11 10:49 ` Liam Girdwood
2010-02-11 11:14 ` [alsa-devel] " Jarkko Nikula
2010-02-11 11:33 ` Mark Brown
2010-02-11 15:02 ` Peter Ujfalusi
2010-02-11 16:42 ` Mark Brown [this message]
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=20100211164227.GA18464@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=Tomi.Valkeinen@nokia.com \
--cc=alsa-devel@alsa-project.org \
--cc=felipe.balbi@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=peter.ujfalusi@nokia.com \
--cc=swirl@gmx.li \
--cc=tony@atomride.com \
--cc=weber@corscience.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.