From: Liam Girdwood <lrg@ti.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Tony Lindgren <tony@atomide.com>,
Misael Lopez Cruz <misael.lopez@ti.com>,
alsa-devel@alsa-project.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 00/10] OMAP4: ASoC: Support for PandaBoard family
Date: Wed, 21 Dec 2011 18:26:23 +0000 [thread overview]
Message-ID: <1324491983.8478.4.camel@odin> (raw)
In-Reply-To: <1323856022-24053-1-git-send-email-peter.ujfalusi@ti.com>
On Wed, 2011-12-14 at 11:46 +0200, Peter Ujfalusi wrote:
> Hello,
>
> the following series will add ASoC support for PandaBoards.
> PandaBoards have different audio routings compared to SDP4430/Blaze boards, but
> the differences not that big to justify a new ASoC machine driver.
>
> Main changes:
> - Rename the sdp4430 ASoC machine driver to use generic name: omap-abe-twl6040
> - Convert the ASoC machine driver to platform driver
> - The type of the board, and the desired sound card name is passed via platform
> data to the ASoC machine driver
> - Based on the board type the driver selects different audio routings
> - Registration of the needed platform devices in board files (sdp4403, panda)
>
> After this series the sound card names will be different for easier UCM
> integration:
> "OMAP4-SDP4430" for SDP4430/Blaze boards
> "OMAP4-Panda" for PandaBoard 4430
> "OMAP4-PandaES" for PandaBoard ES (4460)
>
1,2,3 Applied.
5 & 8 depend on the others so best to resend with Acks if unchanged.
Thanks
Liam
prev parent reply other threads:[~2011-12-21 18:26 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 9:46 [PATCH 00/10] OMAP4: ASoC: Support for PandaBoard family Peter Ujfalusi
2011-12-14 9:46 ` [PATCH 01/10] ASoC: sdp4430: Correct author e-mail address Peter Ujfalusi
2011-12-14 10:06 ` Mark Brown
2011-12-14 9:46 ` [PATCH 02/10] ASoC: OMAP4: Rename the sdp4430 machine driver Peter Ujfalusi
2011-12-14 10:22 ` Mark Brown
2011-12-14 9:46 ` [PATCH 03/10] ASoC: omap-abe-twl6040: Correct internal prefix, Kconfig entry Peter Ujfalusi
2011-12-14 10:23 ` Mark Brown
2011-12-14 9:46 ` [PATCH 04/10] include: platform_data: Platform data header for OMAP4 ASoC audio Peter Ujfalusi
2011-12-14 9:57 ` Mark Brown
2011-12-15 13:02 ` Péter Ujfalusi
2011-12-17 9:36 ` Mark Brown
2011-12-19 14:04 ` Peter Ujfalusi
2011-12-19 19:20 ` Tony Lindgren
2011-12-20 0:47 ` Mark Brown
2011-12-20 0:24 ` Mark Brown
2011-12-14 9:46 ` [PATCH 05/10] OMAP4: 4430sdp: Register platform device for OMAP4 audio Peter Ujfalusi
2011-12-14 18:00 ` Tony Lindgren
2011-12-14 9:46 ` [PATCH 06/10] ASoC: omap-abe-twl6040: Convert to platform deriver Peter Ujfalusi
2011-12-14 10:01 ` Mark Brown
2011-12-14 10:15 ` Péter Ujfalusi
2011-12-14 11:27 ` Mark Brown
2011-12-15 8:17 ` Péter Ujfalusi
2011-12-15 13:01 ` Péter Ujfalusi
2011-12-14 9:47 ` [PATCH 07/10] ASoC: omap-abe-twl6040: Add support for PandaBoard Peter Ujfalusi
2011-12-14 9:47 ` [PATCH 08/10] OMAP4: omap4panda: Enable audio support Peter Ujfalusi
2011-12-14 18:02 ` Tony Lindgren
2011-12-14 9:47 ` [PATCH 09/10] ASoC: omap-abe-twl6040: Add missing audio route information Peter Ujfalusi
2011-12-14 10:14 ` [alsa-devel] " Mark Brown
2011-12-21 18:26 ` 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=1324491983.8478.4.camel@odin \
--to=lrg@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-omap@vger.kernel.org \
--cc=misael.lopez@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).