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 11:39:52 +0100 [thread overview]
Message-ID: <20091006103952.GC10118@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <8bd0f97a0910060300m7fa80daas63afd272ba85fb16@mail.gmail.com>
On Tue, Oct 06, 2009 at 06:00:23AM -0400, Mike Frysinger wrote:
> On Tue, Oct 6, 2009 at 05:50, Mark Brown wrote:
> > These are board-specific drivers to hook things up on a given system
> > (presumably various eval boards), they're the non-generic part of the
> > system that says how the generic DAI and CODEC drivers have been hooked
> > up.
> except the Blackfin machine drivers are written in such a way that
> they arent specific to a board. they'll work on any system with a
> SPORT and a SPI/I2C bus.
That's not 100% clear - some of the drivers say they're specific to
particular designs (either in the help text or by having board-specific
GPIO setup). It's certainly the intention of the API that the board
hookups be fixed at run time rather than at compile time, and that
things like using multiple CPU DAIs should be possible.
The other option here is to make the CODEC drivers build without their
control buses, which keeps the people doing random configurations happy.
next prev parent reply other threads:[~2009-10-06 10:39 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 [this message]
2009-10-06 11:32 ` Mike Frysinger
2009-10-06 11:52 ` Mark Brown
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=20091006103952.GC10118@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.