From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: uclinux-dist-devel@blackfin.uclinux.org, alsa-devel@alsa-project.org
Subject: Re: [Uclinux-dist-devel] [PATCH 2/2] ASoC: Blackfin AD1836/AD1938 machine drivers: require SPI master
Date: Tue, 6 Oct 2009 12:52:17 +0100 [thread overview]
Message-ID: <20091006115216.GA12993@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <8bd0f97a0910060432o67e9d00bu84c0139701709e63@mail.gmail.com>
On Tue, Oct 06, 2009 at 07:32:30AM -0400, Mike Frysinger wrote:
> back to the original issue. the AD1836/AD1938 have their registers
> programed via SPI, but they dont care what SPI bus they're connected
> to. that is specified in the board resources. because of the way the
> Kconfig options are handled (machine drivers select codecs), the
> SPI_MASTER dependency cannot be added to the codec Kconfigs in
> codecs/Kconfig. so even though the SPI dependency is only in the
> codec and not the machine driver, the machine driver needs to declare
> the SPI_MASTER dependency to prevent incorrect config selections and
> link failures.
Or, like I say, the drivers for the CODEC should be changed to allow
build with no control bus. This is a general problem for all the ASoC
drivers and I'm still not sure which way to go. Depending on just SPI
support fixes the random build case but doesn't help end users get the
driver working so it doesn't seem so useful. If we're only going to be
able to fix the random build case then it seems more useful to do so by
having the CODEC driver able to build without the control bus, that way
individual machine drivers don't need to worry about it.
next prev parent reply other threads:[~2009-10-06 11:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 5:51 [PATCH 1/2] ASoC: AD1980/AD73311: make sure to set dev member Mike Frysinger
2009-10-06 5:51 ` [PATCH 2/2] ASoC: Blackfin AD1836/AD1938 machine drivers: require SPI master Mike Frysinger
2009-10-06 9:33 ` Mark Brown
[not found] ` <20091006093325.GA10118-HF5t3jzXg/6ND3a5+9QAFujbO/Zr0HzV@public.gmane.org>
2009-10-06 9:41 ` Mike Frysinger
2009-10-06 9:50 ` [Uclinux-dist-devel] " Mark Brown
2009-10-06 10:00 ` Mike Frysinger
2009-10-06 10:39 ` Mark Brown
2009-10-06 11:32 ` Mike Frysinger
2009-10-06 11:52 ` Mark Brown [this message]
2009-10-06 21:09 ` Mike Frysinger
2009-10-06 22:07 ` Mark Brown
2009-10-07 8:32 ` Mike Frysinger
2009-10-07 10:19 ` Mark Brown
2009-10-08 0:27 ` Mike Frysinger
2009-10-08 10:01 ` Mark Brown
2009-10-09 0:01 ` Mike Frysinger
2009-10-10 3:47 ` Barry Song
[not found] ` <3c17e3570910092047n39db1ac9vfe76b9304897a794-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-10 11:11 ` [alsa-devel] " Mark Brown
[not found] ` <1254808311-3594-1-git-send-email-vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2009-10-06 9:42 ` [alsa-devel] [PATCH 1/2] ASoC: AD1980/AD73311: make sure to set dev member Mark Brown
2009-10-06 9:59 ` [Uclinux-dist-devel] " Mike Frysinger
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=20091006115216.GA12993@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=vapier.adi@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.