From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: Date: Wed, 24 Oct 2007 09:08:55 -0600 From: "Grant Likely" Sender: glikely@secretlab.ca To: "Timur Tabi" Subject: Re: Audio codec device tree entries In-Reply-To: <471F52ED.10007@freescale.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 References: <9e4733910710221859q6ea54810nba58907d5ddd966d@mail.gmail.com> <471E12C7.8020509@freescale.com> <8416ea754e013a67441aec778c81ad73@kernel.crashing.org> <9e4733910710231529h1089eacdy888306f20af92555@mail.gmail.com> <471F52ED.10007@freescale.com> Cc: PowerPC dev list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 10/24/07, Timur Tabi wrote: > > codec0: i2s-codec@0 { > > compatible = "ti,tas5508"; > > reg = <0>; > > i2s-handle = <&i2s@2000>; > > }; > > I'd do this the other way around -- that is: > > i2s@2200 { // PSC2 > compatible = "fsl,mpc5200b-psc-i2s","fsl,mpc5200-psc-i2s"; > ... > i2c-handle = <&codec0>; /* Or something like that */ i2c-handle is a poor property name here. It should be 'codec-handle'. The codec could theoretically live on just about *any* control bus; not just i2c. g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. grant.likely@secretlab.ca (403) 399-0195