From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ola Lilja <ola.o.lilja@stericsson.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Liam Girdwood <lrg@ti.com>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH 8/8] ASoC: Ux500: Add machine-driver
Date: Wed, 2 May 2012 09:17:09 +0100 [thread overview]
Message-ID: <20120502081709.GA4075@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4FA0EBF7.2090903@stericsson.com>
[-- Attachment #1.1: Type: text/plain, Size: 1173 bytes --]
On Wed, May 02, 2012 at 10:10:31AM +0200, Ola Lilja wrote:
> On 04/30/2012 12:04 PM, Mark Brown wrote:
> > The code I'm referring to is this:
> > which is definitely compile time. It's not the factoring stuff out,
> > it's the way it's been done. Library code like Tegra uses isn't a
> > problem but this sort of arrangement does cause problems.
> OK, the thought with this was to be able to activate/deactivate the individual
> codec-drivers since we have several separate codecs on our Ux500-platform (Note
> that in this patch-set there is not patches for the other two codec-drivers).
> Since we already knows at compile-time if any of these three codecs are present
> we did it this ways, being able to add them separately in menuconfig.
This really isn't the idiom mainline is looking for, you should be able
to build a kernel which will boot on multiple boards. There's a reason
why you don't see this sort of ifdef in other code...
> How could we solve this? All three codec-drivers has dependancies to other stuff
> being activated in menuconfig.
Like I say, library style code like Tegra has is totally fine if there's
stuff that can usefully be shared.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2012-05-02 8:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 9:33 [PATCH 8/8] ASoC: Ux500: Add machine-driver Ola Lilja
2012-04-23 19:05 ` Mark Brown
2012-04-27 10:59 ` Ola Lilja
2012-04-27 11:15 ` Mark Brown
2012-04-30 8:26 ` Ola Lilja
2012-04-30 10:04 ` Mark Brown
2012-05-02 8:10 ` Ola Lilja
2012-05-02 8:17 ` Mark Brown [this message]
2012-05-02 8:27 ` Ola Lilja
2012-05-02 8:41 ` Mark Brown
2012-05-02 8:59 ` Ola Lilja
2012-05-02 9:07 ` 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=20120502081709.GA4075@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=linus.walleij@linaro.org \
--cc=lrg@ti.com \
--cc=ola.o.lilja@stericsson.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 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.