From: "Péter Ujfalusi" <peter.ujfalusi@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Liam Girdwood <lrg@ti.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: Re: [PATCH 04/10] include: platform_data: Platform data header for OMAP4 ASoC audio
Date: Thu, 15 Dec 2011 15:02:44 +0200 [thread overview]
Message-ID: <3652535.KtFJC1aH5Z@barack> (raw)
In-Reply-To: <20111214095745.GD3072@opensource.wolfsonmicro.com>
On Wednesday 14 December 2011 17:57:47 Mark Brown wrote:
> On Wed, Dec 14, 2011 at 11:46:57AM +0200, Peter Ujfalusi wrote:
> > +enum board_type {
> > + OMAP_ABE_TWL6040_SDP4430,
> > + OMAP_ABE_TWL6040_PANDA,
> > + OMAP_ABE_TWL6040_PANDA_ES,
> > +};
>
> It seems like it might better in the long run to make this feature based
> rather than enumerating the individual boards - that means that if
> boards mix and match the features or add features on the side of
> additional designs (eg, external amplifiers that need power control)
> it's easier to scale the options.
Yes this is planed for the Dtree support, but the aim here is to get working
audio on PandaBoard as well with upstream kernel.
--
Péter
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-12-15 13:02 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 [this message]
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 ` [PATCH 00/10] OMAP4: ASoC: Support for PandaBoard family Liam Girdwood
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=3652535.KtFJC1aH5Z@barack \
--to=peter.ujfalusi@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=misael.lopez@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