From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.180]) by ozlabs.org (Postfix) with ESMTP id 7B09FDDE04 for ; Wed, 2 Jan 2008 04:42:43 +1100 (EST) Received: by wa-out-1112.google.com with SMTP id m28so8770195wag.13 for ; Tue, 01 Jan 2008 09:42:42 -0800 (PST) Message-ID: <9e4733910801010942y47e4cdbfge5e0d3e44ab96760@mail.gmail.com> Date: Tue, 1 Jan 2008 12:42:42 -0500 From: "Jon Smirl" To: "Timur Tabi" Subject: Re: [PATCH] ASoC drivers for the Freescale MPC8610 SoC In-Reply-To: <9e4733910801010925j67192427o4e0e824b9d7e0ad0@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 References: <11981089894052-git-send-email-timur@freescale.com> <9e4733910801010925j67192427o4e0e824b9d7e0ad0@mail.gmail.com> Cc: linuxppc-dev@ozlabs.org, alsa-devel@alsa-project.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 1/1/08, Jon Smirl wrote: > On 12/19/07, Timur Tabi 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 = ; > > + }; > > + }; > > 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. -- Jon Smirl jonsmirl@gmail.com