public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: brian.austin@cirrus.com (Brian Austin)
To: linux-arm-kernel@lists.infradead.org
Subject: [alsa-devel] [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

  reply	other threads:[~2014-04-30  2:31 UTC|newest]

Thread overview: 33+ 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           ` Mark Brown
2014-05-01 12:26             ` Austin, Brian
2014-05-01  1:30   ` Mark Brown
2014-04-29 11:18 ` [PATCH 03/15] ASoC: SMDK_WM8580_PCM needs REGMAP_I2C Xia Kaixu
2014-05-01  3:30   ` Mark Brown
2014-04-29 11:18 ` [PATCH 04/15] ASoC: samsung-idma: avoid 64-bit division Xia Kaixu
2014-04-30  3:50   ` Tushar Behera
2014-05-01  3:31   ` Mark Brown
2014-04-29 11:18 ` [PATCH 05/15] ASoC: nuc900: export nuc900_ac97_data Xia Kaixu
2014-05-01  3:32   ` Mark Brown
2014-04-29 11:18 ` [PATCH 07/15] ASoC: UDA1380 needs I2C Xia Kaixu
2014-05-01 17:59   ` Mark Brown
2014-04-29 11:18 ` [PATCH 08/15] ASoC: TTC DKB audio " Xia Kaixu
2014-05-01 18:01   ` Mark Brown
2014-04-29 11:18 ` [PATCH 09/15] ASoC: Migo-R sound " Xia Kaixu
2014-05-01 20:30   ` Mark Brown
2014-04-29 11:18 ` [PATCH 10/15] ASoC: TLV320AIC23 and Simtec Hermes audio Xia Kaixu
2014-05-01 20:29   ` Mark Brown
2014-04-29 11:18 ` [PATCH 11/15] ASoC: WM0010 needs SPI Xia Kaixu
2014-05-01 19:08   ` Mark Brown
2014-04-29 11:18 ` [PATCH 13/15] ASoC: SND_S3C_DMA_LEGACY needs S3C24XX_DMA Xia Kaixu
2014-05-01 19:11   ` Mark Brown
2014-05-01 22:35     ` Arnd Bergmann
2014-05-02 10:25       ` Heiko Stübner
2014-05-02 16:10         ` Arnd Bergmann
2014-05-02 17:26         ` Mark Brown
2014-05-02 17:24       ` Mark Brown
2014-04-29 11:18 ` [PATCH 15/15] ASoC: pxa: remove mach header dependency Xia Kaixu

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=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