From: Brian Austin <brian.austin@cirrus.com>
To: Xia Kaixu <kaixu.xia@linaro.org>
Cc: alsa-devel@alsa-project.org, linaro-kernel@lists.linaro.org,
arnd@arndb.de, Sangbeom Kim <sbkim73@samsung.com>,
Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org, Timur Tabi <timur@tabi.org>,
linux-samsung-soc@vger.kernel.org,
Lars-Peter Clausen <lars@metafoo.de>,
Ben Dooks <ben-linux@fluff.org>,
linux-input@vger.kernel.org, Kukjin Kim <kgene.kim@samsung.com>,
linux-arm-kernel@lists.infradead.org,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 01/15] ASoC: CS42L51 and WM8962 codecs depend on INPUT
Date: Tue, 29 Apr 2014 21:31:30 -0500 [thread overview]
Message-ID: <alpine.DEB.2.02.1404292124270.31465@heelrod> (raw)
In-Reply-To: <1398770316-19715-2-git-send-email-kaixu.xia@linaro.org>
On Tue, 29 Apr 2014, Xia Kaixu wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> Building ARM randconfig got into a situation where CONFIG_INPUT
> is turned off and SND_SOC_ALL_CODECS is turned on, which failed
> for two codecs trying to use the input subsystem. Some other
> drivers also select one of these codecs and consequently need an
> explicit dependency added.
I assume you mean the CS42L52 instead of the L51. INPUT is used for a BEEP
Generator but when I disable CONFIG_INPUT I do not get an error. Is there
any information available on what the error is?
>
> Appending to the dependency list seems the easiest way out,
> since this is not a practical limitation. If anyone really
> needs to build these codecs for a kernel with no input support,
> a more sophisticated solution can be implemented.
>
It shouldn't build the BEEP code without CONFIG_INPUT enabled as you can
use the CODEC without the BEEP enabled.
I believe the WM8962 is done the same way.
Thanks,
Brian
next prev parent reply other threads:[~2014-04-30 2:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1398770316-19715-1-git-send-email-kaixu.xia@linaro.org>
2014-04-29 11:18 ` [PATCH 01/15] ASoC: CS42L51 and WM8962 codecs depend on INPUT Xia Kaixu
2014-04-30 2:31 ` Brian Austin [this message]
2014-05-01 1:31 ` [alsa-devel] " Mark Brown
2014-05-01 1:54 ` Austin, Brian
2014-05-01 2:16 ` Austin, Brian
2014-05-01 3:27 ` [alsa-devel] " Mark Brown
2014-05-01 12:26 ` Austin, Brian
2014-05-01 1:30 ` 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=alpine.DEB.2.02.1404292124270.31465@heelrod \
--to=brian.austin@cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=arnd@arndb.de \
--cc=ben-linux@fluff.org \
--cc=broonie@kernel.org \
--cc=kaixu.xia@linaro.org \
--cc=kgene.kim@samsung.com \
--cc=lars@metafoo.de \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=sbkim73@samsung.com \
--cc=timur@tabi.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