From mboxrd@z Thu Jan 1 00:00:00 1970 From: Scott Wood Subject: Re: [PATCH] ASoC drivers for the Freescale MPC8610 SoC Date: Thu, 03 Jan 2008 12:54:10 -0600 Message-ID: <477D2F52.7090306@freescale.com> References: <11981089894052-git-send-email-timur@freescale.com> <9e4733910801010925j67192427o4e0e824b9d7e0ad0@mail.gmail.com> <9e4733910801010942y47e4cdbfge5e0d3e44ab96760@mail.gmail.com> <477BAB67.4080003@freescale.com> <477D24AA.4050804@freescale.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from az33egw01.freescale.net (az33egw01.freescale.net [192.88.158.102]) by alsa0.perex.cz (Postfix) with ESMTP id 0E2A9103865 for ; Thu, 3 Jan 2008 19:54:14 +0100 (CET) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Grant Likely Cc: linuxppc-dev@ozlabs.org, alsa-devel@alsa-project.org, Timur Tabi List-Id: alsa-devel@alsa-project.org Grant Likely wrote: > On 1/3/08, Timur Tabi wrote: >> Grant Likely wrote: >> >>> Why not be a child of the i2c bus with a phandle to the ssi bus? >> Because when I probe the SSI node, I want to know what the attached codec is. >> So if anything, I would need a pointer from the SSI bus *to* the respective >> child on the I2C bus. > > That's fine too (it's what is done with Ethernet PHYs). My preference > is the other way around, but it's not a big issue in this case. I'd just link in both directions, and let software follow it in whichever direction it prefers. -Scott