public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@nokia.com>
To: alsa-devel@alsa-project.org
Cc: "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: [PATCHv3 3/4] Add ASoC support for DevKit8000
Date: Thu, 11 Feb 2010 17:02:54 +0200	[thread overview]
Message-ID: <201002111702.54783.peter.ujfalusi@nokia.com> (raw)
In-Reply-To: <20100211131418.9521c603.jhnikula@gmail.com>

On Thursday 11 February 2010 13:14:18 ext Jarkko Nikula wrote:
> On Thu, 11 Feb 2010 10:49:48 +0000
> 
> Liam Girdwood <lrg@slimlogic.co.uk> wrote:
> > I do agree this makes good sense for boards that are very similar and
> > have different audio options/config, but in this case the ASoC mach
> > drivers are identical (atm). Imo it just makes more sense to keep the
> > one Kconfig.
> 
> 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
> driver, the defconfigs are anyway have to modify so it's better stay
> with the original patch:

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.

> 
> http://mailman.alsa-project.org/pipermail/alsa-devel/2010-February/025129.h
> tml
> 
> Sorry about line noise, Thomas :-)
> 

-- 
Péter

  parent reply	other threads:[~2010-02-11 15:02 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 [this message]
2010-02-11 16:42           ` 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=201002111702.54783.peter.ujfalusi@nokia.com \
    --to=peter.ujfalusi@nokia.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox