On 1/1/08, Jon Smirl jonsmirl@gmail.com wrote:
On 12/19/07, Timur Tabi timur@freescale.com wrote:
ssi@16000 {compatible = "fsl,ssi";cell-index = <0>;reg = <16000 100>;interrupt-parent = <&mpic>;interrupts = <3e 2>;fsl,mode = "i2s-slave";codec {compatible = "cirrus,cs4270";/* MCLK source is a stand-alone oscillator */bus-frequency = <bb8000>;};};Does this need to be bus-frequency? It's always called MCLK in all of the literature.
In my case the MCLK comes from a chip on the i2c bus that is programmable How would that be encoded?.
Looking at the cs4270 codec driver it is controlled by i2c (supports SPI too). What happened to the conversation about putting codecs on the controlling bus and then linking them to the data bus?
If that's the case the cs4270 should be in the i2c bus node (missing currently) and then a link from the SSI bus would point to it.
cs4270 is still an old style i2c driver which is going to get deprecated. It takes about thirty minutes to convert it to new style. If was new style it could pick up its i2c address from the device tree instead of searching for it.