public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: robert.jarzmik@free.fr (Robert Jarzmik)
To: linux-arm-kernel@lists.infradead.org
Subject: [alsa-devel] [PATCH] ASoC: pxa: add I2C dependencies as needed
Date: Tue, 03 Jun 2014 23:12:09 +0200	[thread overview]
Message-ID: <87k38xg0k6.fsf@free.fr> (raw)
In-Reply-To: <46560700.2S4p0nUZl8@wuerfel> (Arnd Bergmann's message of "Tue, 03 Jun 2014 20:38:27 +0200")

Arnd Bergmann <arnd@arndb.de> writes:

> We have in the past added 'depends on I2C' for some of the PXA boards
> after hitting randconfig build bugs. I have seens a couple of new
> bugs in this area during the linux-next cycle for 3.16, after it
> became possible to build some more PXA machines with I2C disabled.
>
> To shut this up for good, this adds the dependency to every board
> that uses I2C as the interface to the codec. I have gone through
> all board files and verified that they all either use AC97 or
> I2C, and this annotates the latter. Some of these already enable
> I2C from mach-pxa/Kconfig, but since that can change it's better
> to be explicit here.
>
> The link error that can result otherwise happens when CONFIG_I2C
> is set to 'm' and the codec driver is built-in as a result of being
> selected by the platform specific glue.

Hi Arnd,

Any reason SND_PXA2XX_SOC_MIOA701 escaped ? The board is PXA based, and its
codec wm9713 is I2C based, and relies on AC97.

Cheers.

-- 
Robert

  reply	other threads:[~2014-06-03 21:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-03 18:38 [PATCH] ASoC: pxa: add I2C dependencies as needed Arnd Bergmann
2014-06-03 21:12 ` Robert Jarzmik [this message]
2014-06-03 21:59   ` [alsa-devel] " Mark Brown
2014-06-04 19:40     ` Robert Jarzmik
2014-06-03 22:00 ` 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=87k38xg0k6.fsf@free.fr \
    --to=robert.jarzmik@free.fr \
    --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