On Thu, Mar 15, 2012 at 11:57:52AM -0400, Trent Piepho wrote:
which caused text window in gmail to become deselected, which caused a subsequent enter to send the email rather than creating a new line.
For esai, would you add something like: esai-controller = <&esai1>; esai-audio-codec = <&sgtl5000_3>;
That seems rather ugly to me.
None of these examples seem particularly to reflect realistic audio hardware; they're more describing a board with multiple distinct audio subsystems on it than a single card. Remember that nothing at all is fixed about how the card binding works internally, the card driver is free to pick any binding that makes sense for the systems it supports. Shoehorning every possible card into the same binding is definitely a really bad idea.
It seems to me in most device bindings where one piece of hardware is attached to another, than the one upstream has in its binding a phandle to the one downstream. But here we have a third binding with two lists of devices and an implied link between devices in corresponding positions in the lists. Does any other device binding work like that?
There's no upstream and downstream here, really. But like I say none of this looks like realistic hardware anyway.
*Please* go and read the previous discussions of audio bindings for SoCs, while it's more understandable with people who haven't been involved before its still tiresome to have to go back to square one.