From: Mike Frysinger <vapier.adi@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Barry Song <21cnbao@gmail.com>,
lrg@slimlogic.co.uk, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] New ASoC Drivers for ADI AD1938 codec
Date: Fri, 19 Jun 2009 07:05:48 -0400 [thread overview]
Message-ID: <8bd0f97a0906190405k33503d8ekd74ec9ddbb2fde12@mail.gmail.com> (raw)
In-Reply-To: <20090619104738.GF5270@sirena.org.uk>
On Fri, Jun 19, 2009 at 06:47, Mark Brown wrote:
> On Fri, Jun 19, 2009 at 05:28:15PM +0800, Barry Song wrote:
>> 1. add AD1938 codec driver (codec)
>> 2. add blackfin SPORT-TDM DAI and PCM driver (platform)
>> 3. add bf5xx board with AD1938 driver (machine)
>
> As Liam said you really need to submit this as a patch series rather
> than as a single big patch - as your commit log here indicates you've
> got several different things going on here.
blah, i had this queued locally with a "todo:split". wanted to wait
for Barry to finish developing the driver first though.
at any rate, i hate to sound like a broken record wrt my alsa
ignorance, but i'm thinking the logical split would be like Barry
numbered it -- one patch for sound/codec/, one patch for the TDM
transport, and one patch for hooking up the AD1938 to TDM.
>> +static int __devinit ad1938_spi_probe(struct spi_device *spi)
>> +{
>> + spi->dev.power.power_state = PMSG_ON;
>> + ad1938_socdev->card->codec->control_data = spi;
>> +
>> + return 0;
>> +}
>> +
>> +static int __devexit ad1938_spi_remove(struct spi_device *spi)
>> +{
>> + return 0;
>> +}
>
> Your device probing should all be restructured so that the SPI device
> for the CODEC is registered as any other SPI device rather than being
> set up as part of probing the ASoC device. See the wm8731 driver for
> an example of doing this for a SPI device.
>
> This will require that the arch code for any systems with the ad1938
> do the setup of the device.
so should sound/soc/blackfin/bf5xx-ad1938.c even exist in the first place ?
-mike
next prev parent reply other threads:[~2009-06-19 11:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 9:28 Barry Song
2009-06-19 9:35 ` Liam Girdwood
2009-06-19 9:41 ` Liam Girdwood
2009-06-19 10:47 ` Mark Brown
2009-06-19 11:05 ` Mike Frysinger [this message]
2009-06-19 11:13 ` Mark Brown
2009-06-19 11:21 ` Mike Frysinger
2009-06-19 11:56 ` Mark Brown
2009-06-20 23:15 ` [alsa-devel] " Robin Getz
2009-06-21 0:13 ` Mark Brown
[not found] ` <3c17e3570906212008n6071e987sbcd4b9377364ae78@mail.gmail.com>
2009-06-22 10:57 ` Mark Brown
[not found] ` <3c17e3570906220600l3471b6f0rc29c674b4a5ec2df@mail.gmail.com>
2009-06-22 13:11 ` Mark Brown
2009-07-13 8:12 ` 宋宝华
2009-07-13 9:15 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2009-06-19 5:58 Barry Song
2009-06-19 6:44 ` 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=8bd0f97a0906190405k33503d8ekd74ec9ddbb2fde12@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=21cnbao@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
/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
all inboxes | Powered by JetHome®