From: Ola Lilja <ola.o.lilja@stericsson.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.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 10:59:53 +0200 [thread overview]
Message-ID: <4FA0F789.20708@stericsson.com> (raw)
In-Reply-To: <20120502084104.GB4075@opensource.wolfsonmicro.com>
On 05/02/2012 10:41 AM, Mark Brown wrote:
> 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.
Yes, but the codec-driver has dependency to another driver. For AB8500
codec-driver it needs the MFD-driver. This AB8500-core driver can be deselected
in menuconfig and then our whole ASoC-driver will be unavailable, even though
the other two codec-drivers actually could be used.
next prev parent reply other threads:[~2012-05-02 9:00 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
2012-05-02 8:59 ` Ola Lilja [this message]
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=4FA0F789.20708@stericsson.com \
--to=ola.o.lilja@stericsson.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linus.walleij@linaro.org \
--cc=lrg@ti.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.