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 10:07:08 +0100 [thread overview]
Message-ID: <20120502090708.GE4075@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4FA0F789.20708@stericsson.com>
[-- Attachment #1.1: Type: text/plain, Size: 723 bytes --]
On Wed, May 02, 2012 at 10:59:53AM +0200, Ola Lilja wrote:
> 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.
I'm really having a hard time seeing this as a problem, especially given
that the ab8500 is the core system PMIC so there's a whole raft of
additional functionality that'd be lost. I'd also be surprised if the
interconnects between the devices could be expressed without excessive
pain, or alternatively if there's no interconnects I'd expect to see
multiple sound cards.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2012-05-02 9:07 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
2012-05-02 9:07 ` Mark Brown [this message]
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=20120502090708.GE4075@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).