Re: [PATCH 04/10] include: platform_data: Platform data header for OMAP4 ASoC audio

[Mark Brown <broonie@opensource.wolfsonmicro.com>]

On Mon, Dec 19, 2011 at 04:04:53PM +0200, Peter Ujfalusi wrote:
> On 12/17/2011 11:36 AM, Mark Brown wrote:

> > Just do it right to start off with, the device tree bindings should
> > normally map closely onto the platform data where platform data exists
> > already and you're going to have to have the code structured by feature
> > anyway.

> I do not want to 'bloat' the board files under mach-omap2 for sdp4430,
> Panda with string arrays to pass the DAPM routing from there to the ASoC
> machine driver to construct the board specific routing.

I don't know that you need to push the full DAPM table down there,
there's certainly way more compact ways of representing selections like
this.

> All of this sort of thing will go away with DT in the future (including
> the platform_data).

I'm not really happy with this as a reason for pushing low quality stuff
in - either the code isn't going to be around long so we may as well
jump to what we meant to do or it's going to be there for long enough
that people will have to work with it (and perhaps pick it up as a
reference).

> struct omap-abe-twl6040-connection {
> 	const char *sink;
> 	const char *source;
> };

omap-abe-mcbsp--mcpdm-twl4030?  :P

To be honest if you're going to do this I don't understand why you'd
bother defining this type which you'll just have to translate into a
dapm_route.