From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: Barry Song <21cnbao@gmail.com>,
"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] New ASoC Drivers for ADI AD1938 codec
Date: Fri, 19 Jun 2009 12:56:13 +0100 [thread overview]
Message-ID: <FD8E5377-D9B2-4876-8A82-F2E29BA3B2E4@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <8bd0f97a0906190421q332f337cr1799c6b65bd06f0e@mail.gmail.com> (sfid-20090619_122210_786837_40A5C757)
On 19 Jun 2009, at 12:21, Mike Frysinger <vapier.adi@gmail.com> wrote:
> On Fri, Jun 19, 2009 at 07:13, Mark Brown wrote:
>>>>
>>>
>>>
>>
>>>>
>>>>
>>>
>> Yes. It is needed in order to specify how things are hooked up on a
>> given
>> board.
>
> to look at the wm8731 then, these are good examples of how it's done ?
> sound/soc/atmel/sam9g20_wm8731.c
> sound/soc/pxa/corgi.c
Anything should be OK - possibly one of the existing Blackfin drivers.
I mentioned wm8731 due to the SPI but by the time it gets to the
machine driver that's hidden so it's not urgently relevant.
next prev parent reply other threads:[~2009-06-19 11:58 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
2009-06-19 11:13 ` Mark Brown
2009-06-19 11:21 ` Mike Frysinger
2009-06-19 11:56 ` Mark Brown [this message]
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=FD8E5377-D9B2-4876-8A82-F2E29BA3B2E4@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=21cnbao@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--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 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®