On Wed, Oct 10, 2012 at 05:51:27PM +0900, Mark Brown wrote: > On Wed, Oct 10, 2012 at 10:40:06AM +0200, Sascha Hauer wrote: > > > Mark, when do we get the same for aSoC? ;) > > Well, I'm unlikely to work on it as I don't have any systems which can > boot with device tree. If it's only that I'm sure we could spare a i.MX53 LOCO ;) > > The big, big problem you've got doing this is lots of dynamic changes at > runtime and in general complicated systems. It's trivial to describe > the physical links but they don't provide anything like enough > information to use things. Quite frankly I'm not sure device tree is a > useful investment of time for advanced audio systems anyway, it's really > not solving any problems people actually have. Right now the i.MX audmux binding is only enough to say which ports should be connected, but not which format should be used. Just today we had the problem where a codec has two DAIs and wanted to add the information on which port our SSI unit is connected to the devicetree. So I think it's worthwile to do, but that would be a big big task... Sascha -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
