On Wed, Oct 10, 2012 at 11:21:15AM +0200, Sascha Hauer wrote: > On Wed, Oct 10, 2012 at 05:51:27PM +0900, Mark Brown wrote: > > 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 ;) Well, something with Wolfson hardware would be helpful. > > 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 Why should that be in DT? For most things it's either fixed by the hardware or makes no odds. > 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. There's nothing stopping you doing that right now, the existing DT > So I think it's worthwile to do, but that would be a big big task... For simple devices there's already stuff there and it's not hard to add new machine bindings, it's trying to cover the general case that's far too much effort. -- 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
