On Sun, Apr 7, 2013 at 11:00 AM, Fabio Estevam <[email protected]> wrote: > On Sun, Apr 7, 2013 at 12:50 PM, Matt Sealey <[email protected]> wrote: > >> If we're dealing with audio codecs, fix the audio codec to accept a >> *table* of possible clock values and if that hardware operates >> differently per clock value, then add that data in there too (like the >> cs42l52 audio codec). Where the software and hardware is a little more >> dynamic, the same binding works here - and the usual trick is just >> force one configuration possible out of many. The board designer can >> look at all the possibilities and choose the one or two or all that >> will work with the design, and it can go into the device tree. > > Sorry, but I have a hard time following a so long response. > > Can't you just send patches to the list with your proposal so that we > can move forward with the idea?
Sure. -- Matt Sealey <[email protected]> Product Development Analyst, Genesi USA, Inc. _______________________________________________ devicetree-discuss mailing list [email protected] https://lists.ozlabs.org/listinfo/devicetree-discuss
