From: Timur Tabi <timur@freescale.com>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: ALSA-devel <alsa-devel@alsa-project.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: Thoughts on ASOC v2 driver architecture
Date: Mon, 16 Jun 2008 11:24:26 -0500 [thread overview]
Message-ID: <485693BA.9010801@freescale.com> (raw)
In-Reply-To: <9e4733910806160923u1e7b3688tba4af776db2ddeef@mail.gmail.com>
Jon Smirl wrote:
> The driver stays in sound/soc/fsl. It's only the creation of the
> device that moves. You just need to add this to
> arch/powerpc/platforms/86xx/mpc8610_hpcd.c and remove it from
> mpc8610_hpcd.c. Adding this to
> arch/powerpc/platforms/86xx/mpc8610_hpcd.c will have no effect if the
> mpc8610_hpcd.c driver is not to be found.
Ok, I'll do that.
> You've complicated it by creating two fabric devices but I believe
> your code could be changed to only make one.
>
> static struct platform_device alsa_fabric = {
> .name = "MPC8610HPCD",
> .id = -1,
> };
>
> static struct platform_device *devices[] = {
> &alsa_fabric,
> };
>
> platform_add_devices(&devices[0], ARRAY_SIZE(devices));
>
>
> I'd rename the driver to something less generic.
> .name = "MPC8610HPCD-fabric",
These are all good ideas. Thanks.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2008-06-16 16:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-15 18:10 Thoughts on ASOC v2 driver architecture Jon Smirl
2008-06-16 10:39 ` Liam Girdwood
2008-06-16 13:26 ` Jon Smirl
2008-06-16 14:23 ` Timur Tabi
2008-06-16 14:32 ` Jon Smirl
2008-06-16 15:03 ` Mark Brown
2008-06-16 15:36 ` Timur Tabi
2008-06-16 15:45 ` Mark Brown
2008-06-16 15:49 ` Timur Tabi
2008-06-16 17:03 ` Mark Brown
2008-06-16 17:10 ` Timur Tabi
2008-06-16 15:53 ` Jon Smirl
2008-06-16 16:01 ` Timur Tabi
2008-06-16 16:23 ` Jon Smirl
2008-06-16 16:24 ` Timur Tabi [this message]
2008-06-17 0:58 ` Jon Smirl
2008-06-17 14:55 ` Timur Tabi
2008-06-16 16:11 ` Jon Smirl
2008-06-16 16:58 ` Mark Brown
2008-06-16 17:00 ` Timur Tabi
2008-06-16 16:24 ` Mark Brown
2008-06-16 15:34 ` Timur Tabi
2008-06-16 13:47 ` Jon Smirl
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=485693BA.9010801@freescale.com \
--to=timur@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jonsmirl@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.