From: Liam Girdwood <lg@opensource.wolfsonmicro.com>
To: Seth Forshee <seth.forshee@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel <alsa-devel@alsa-project.org>,
Timur Tabi <timur@freescale.com>,
Nobin Mathew <nobin.mathew@gmail.com>
Subject: Re: [RFC][ASoC] New device/driver arch
Date: Fri, 15 Jun 2007 16:36:38 +0100 [thread overview]
Message-ID: <1181921798.26658.77.camel@localhost.localdomain> (raw)
In-Reply-To: <d35cec70706150801p2cd29fa4lbd2718048c461f5b@mail.gmail.com>
On Fri, 2007-06-15 at 10:01 -0500, Seth Forshee wrote:
> Hi Liam,
>
> On 6/14/07, Liam Girdwood <lg@opensource.wolfsonmicro.com> wrote:
>
> > Example machine driver for Mainstone with WM8753 is here :-
> >
> > http://opensource.wolfsonmicro.com/cgi-bin/gitweb/gitweb.cgi?p=linux-2.6-asoc;a=blob;f=sound/soc/pxa/mainstone_wm8753.c;h=a49c1c528063494aeadee26ea3e07405c3a8762e;hb=ppc-dev
> >
> > The machine driver now also does the I2C/SPI probing (instead of the
> > codec) and also does any codec IO (to better support multiple
> > controllers).
> >
>
> The way in which the platform device is created in this file seems to
> have a problem. The mainstone_wm8753_probe() function (along
> everything else after that point) seems to expect that the platform
> device will be encapsulated in a struct snd_soc_machine, but this
> doesn't seem to be the case since you are instantiating the device
> with platform_driver_probe(). Am I missing something?
Your right. This is a bug. Will fix.
Thanks
Liam
prev parent reply other threads:[~2007-06-15 15:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 17:40 [RFC][ASoC] New device/driver arch Liam Girdwood
2007-06-14 18:06 ` Manuel Lauss
2007-06-15 9:04 ` Liam Girdwood
2007-06-15 12:06 ` Nobin Mathew
2007-06-15 15:40 ` Liam Girdwood
2007-06-15 15:01 ` Seth Forshee
2007-06-15 15:36 ` Liam Girdwood [this message]
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=1181921798.26658.77.camel@localhost.localdomain \
--to=lg@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=nobin.mathew@gmail.com \
--cc=seth.forshee@gmail.com \
--cc=timur@freescale.com \
--cc=tiwai@suse.de \
/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.