From: Peter Huewe <PeterHuewe@gmx.de>
To: Liam Girdwood <lrg@slimlogic.co.uk>
Cc: linux-sh@vger.kernel.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>,
Kuninori Morimoto <morimoto.kuninori@renesas.com>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: [PATCH] soc/sh: Fix I2C dependency for SND_FSI_AK4642
Date: Mon, 14 Jun 2010 17:39:41 +0200 [thread overview]
Message-ID: <201006141739.42346.PeterHuewe@gmx.de> (raw)
From: Peter Huewe <peterhuewe@gmx.de>
The config option SND_FSI_AK4642 selects SND_SOC_AK464 which in turn
enables the compilation of ak4642.c - however this codec uses I2C to
communicate with the HW.
Consequently when I2C is not set, the compilation fails [1]
This patch fixes this issues.
Signed-off-by: Peter Huewe <peterhuewe@gmx.de>
---
References:
[1] http://kisskb.ellerman.id.au/kisskb/buildresult/2709408/
KernelVersion: linux-next 20100614
sound/soc/sh/Kconfig | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/sound/soc/sh/Kconfig b/sound/soc/sh/Kconfig
index a1d14bc..d26b815 100644
--- a/sound/soc/sh/Kconfig
+++ b/sound/soc/sh/Kconfig
@@ -50,6 +50,7 @@ config SND_FSI_AK4642
bool "FSI-AK4642 sound support"
depends on SND_SOC_SH4_FSI
select SND_SOC_AK4642
+ select I2C
help
This option enables generic sound support for the
FSI - AK4642 unit
--
1.6.4.4
next reply other threads:[~2010-06-14 15:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-14 15:39 Peter Huewe [this message]
2010-06-14 16:10 ` Mark Brown
2010-06-15 14:49 ` Peter Hüwe
2010-06-15 15:19 ` Mark Brown
2010-06-15 15:38 ` [PATCH v2] soc/sh: Fix I2C dependency for SND_FSI_AK4642 and SND_FSI_DA7210 Peter Huewe
2010-06-16 3:54 ` Paul Mundt
2010-06-16 7:43 ` Mark Brown
2010-06-16 7:49 ` Paul Mundt
2010-06-16 7:58 ` Mark Brown
2010-06-16 15:43 ` 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=201006141739.42346.PeterHuewe@gmx.de \
--to=peterhuewe@gmx.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=g.liakhovetski@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=morimoto.kuninori@renesas.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
/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
Powered by JetHome