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:41:04 +0100 [thread overview]
Message-ID: <20120502084104.GB4075@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4FA0F008.4020108@stericsson.com>
[-- Attachment #1.1: Type: text/plain, Size: 517 bytes --]
On Wed, May 02, 2012 at 10:27:52AM +0200, Ola Lilja wrote:
> I'm actually no fan of ifdefs, but let's say that the HDMI-driver is not
> activated in menuconfig. This would lead to the point where the ASoC-driver
> cannot be activated at all, although there is two codecs in the driver which
> could have been used fine.
> If this is the way forwards then I'll rewrite it this way.
The actual CODECs are supposed to be selected by the machine driver
anyway so there should be no possibility of them not being there.
[-- 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:41 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
2012-05-02 8:27 ` Ola Lilja
2012-05-02 8:41 ` Mark Brown [this message]
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=20120502084104.GB4075@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).