From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ASoC: Tegra and i.MX are mutually exclusive
Date: Mon, 24 Jun 2013 18:00:13 +0200 [thread overview]
Message-ID: <2742661.EnTVWyoBzK@wuerfel> (raw)
In-Reply-To: <51C86588.5020606@wwwdotorg.org>
On Monday 24 June 2013 09:28:08 Stephen Warren wrote:
> On 06/24/2013 09:04 AM, Arnd Bergmann wrote:
> > Both Tegra and i.MX provide ac97 operations, which can only
> > exist once in the kernel. They can both be built as loadable
> > modules (only one of them needs to be loaded anyway), but we
> > have to disallow enabling them both as built-in.
>
> > diff --git a/sound/soc/fsl/Kconfig b/sound/soc/fsl/Kconfig
>
> > menuconfig SND_IMX_SOC
> > tristate "SoC Audio for Freescale i.MX CPUs"
> > depends on ARCH_MXC
> > + depends on SND_SOC_TEGRA=n || (SND_SOC_TEGRA=m && m)
>
> I can easily see how this prevents adding SND_IMX_SOC to a config if
> SND_SOC_TEGRA is enabled, but I'm not sure about the other way around;
> does Kconfig check that adding a new SND_SOC_TEGRA wouldn't invalidate
> any of the depends of any already-selected options?
If you start out with a config that has SND_IMX_SOC and select
SND_SOC_TEGRA, SND_IMX_SOC gets turned off.
> In other words, do you need to make the "same" change to Tegra?
No, that would create a circular dependency that is not allowed
in Kconfig.
Arnd
next prev parent reply other threads:[~2013-06-24 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 15:04 [PATCH] ASoC: Tegra and i.MX are mutually exclusive Arnd Bergmann
2013-06-24 15:28 ` Stephen Warren
2013-06-24 16:00 ` Arnd Bergmann [this message]
2013-06-25 6:36 ` [alsa-devel] " Lars-Peter Clausen
2013-06-25 9:26 ` 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=2742661.EnTVWyoBzK@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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).