From: Mark Brown <broonie@sirena.org.uk>
To: David Brownell <david-b@pacbell.net>
Cc: arunks@mistralsolutions.com, alsa-devel@alsa-project.org,
linux-omap@vger.kernel.org, steve@sakoman.com
Subject: Re: [alsa-devel] [PATCH] ASoC: Fix TW4030 Kconfig dependency
Date: Tue, 25 Nov 2008 20:04:15 +0000 [thread overview]
Message-ID: <20081125200411.GA6572@sirena.org.uk> (raw)
In-Reply-To: <200811251054.29156.david-b@pacbell.net>
On Tue, Nov 25, 2008 at 10:54:28AM -0800, David Brownell wrote:
> I'm not sure what you mean by "machine driver" ... there seem
> to be two: arch/arm/mach-omap2/board-*.c for everything except
> ALSA, and then sound/soc/omap/*.c for the ASoC bits.
I meant the arch/arm one.
> As a rule, it's worth avoiding "select" in Kconfig; it doesn't
> work well, since it won't even report missing dependencies much
> less fix the trivial ones.
Right, I'm just thinking that for something like this it might not be
worth turning off the TWL4030 core support given that these sorts of
southbridgeish chips tend to be pretty key to the system. It was just
an idle thought, anyway.
BTW, it'd also be really handy if you could remove the OMAP dependencies
from TWL4030_CORE - I know it currently needs them to actually be useful
at runtime but it'd mean that it's possible to build things like the
codec driver on other configs which helps when working on subsystems.
next prev parent reply other threads:[~2008-11-25 20:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 4:26 [PATCH] ASoC: Fix TW4030 Kconfig dependency arunks
2008-11-25 4:44 ` David Brownell
2008-11-25 15:30 ` Mark Brown
2008-11-25 18:54 ` [alsa-devel] " David Brownell
2008-11-25 20:04 ` Mark Brown [this message]
2008-11-25 20:14 ` David Brownell
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=20081125200411.GA6572@sirena.org.uk \
--to=broonie@sirena.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=arunks@mistralsolutions.com \
--cc=david-b@pacbell.net \
--cc=linux-omap@vger.kernel.org \
--cc=steve@sakoman.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