From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Jarkko Nikula <jhnikula@gmail.com>
Cc: alsa-devel@alsa-project.org, weber@corscience.de,
Thomas Weber <swirl@gmx.li>,
Tomi.Valkeinen@nokia.com, tony@atomride.com,
felipe.balbi@nokia.com, linux-omap@vger.kernel.org
Subject: Re: [PATCHv3 3/4] Add ASoC support for DevKit8000
Date: Thu, 11 Feb 2010 10:49:48 +0000 [thread overview]
Message-ID: <1265885388.3179.8.camel@odin> (raw)
In-Reply-To: <20100211124022.ec6573dc.jhnikula@gmail.com>
On Thu, 2010-02-11 at 12:40 +0200, Jarkko Nikula wrote:
> On Thu, 11 Feb 2010 09:55:12 +0000
> Liam Girdwood <lrg@slimlogic.co.uk> wrote:
>
> > Since this shares the same mach driver as beagle you should share the
> > Kconfig option too (like the Overo).
> >
> Heh, I had just an opposite view :-)
>
> http://mailman.alsa-project.org/pipermail/alsa-devel/2010-February/025124.html
>
>
Heh, didn't see that. ;)
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.
Liam
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
next prev parent reply other threads:[~2010-02-11 10:49 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 [this message]
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 ` [alsa-devel] " 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=1265885388.3179.8.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=Tomi.Valkeinen@nokia.com \
--cc=alsa-devel@alsa-project.org \
--cc=felipe.balbi@nokia.com \
--cc=jhnikula@gmail.com \
--cc=linux-omap@vger.kernel.org \
--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