From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <jonsmirl@gmail.com>
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.178])
	by ozlabs.org (Postfix) with ESMTP id 157BBDDE21
	for <linuxppc-dev@ozlabs.org>; Wed,  2 Jan 2008 04:25:33 +1100 (EST)
Received: by wa-out-1112.google.com with SMTP id m28so8761747wag.13
	for <linuxppc-dev@ozlabs.org>; Tue, 01 Jan 2008 09:25:32 -0800 (PST)
Message-ID: <9e4733910801010925j67192427o4e0e824b9d7e0ad0@mail.gmail.com>
Date: Tue, 1 Jan 2008 12:25:32 -0500
From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Timur Tabi" <timur@freescale.com>
Subject: Re: [PATCH] ASoC drivers for the Freescale MPC8610 SoC
In-Reply-To: <11981089894052-git-send-email-timur@freescale.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
References: <11981089894052-git-send-email-timur@freescale.com>
Cc: linuxppc-dev@ozlabs.org, alsa-devel@alsa-project.org
List-Id: Linux on PowerPC Developers Mail List <linuxppc-dev.ozlabs.org>
List-Unsubscribe: <https://ozlabs.org/mailman/listinfo/linuxppc-dev>,
	<mailto:linuxppc-dev-request@ozlabs.org?subject=unsubscribe>
List-Archive: <http://ozlabs.org/pipermail/linuxppc-dev>
List-Post: <mailto:linuxppc-dev@ozlabs.org>
List-Help: <mailto:linuxppc-dev-request@ozlabs.org?subject=help>
List-Subscribe: <https://ozlabs.org/mailman/listinfo/linuxppc-dev>,
	<mailto:linuxppc-dev-request@ozlabs.org?subject=subscribe>

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?.

-- 
Jon Smirl
jonsmirl@gmail.com