From mboxrd@z Thu Jan 1 00:00:00 1970 From: Timur Tabi Subject: Re: [PATCH] ASoC drivers for the Freescale MPC8610 SoC Date: Thu, 03 Jan 2008 12:16:19 -0600 Message-ID: <477D2673.5090203@freescale.com> References: <11981089894052-git-send-email-timur@freescale.com> <9e4733910801012027p4be16b92r43af773f4e5ae531@mail.gmail.com> <477BADF5.9060003@freescale.com> <20080102184957.GB2007@sirena.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from az33egw02.freescale.net (az33egw02.freescale.net [192.88.158.103]) by alsa0.perex.cz (Postfix) with ESMTP id F2B2110383B for ; Thu, 3 Jan 2008 19:15:10 +0100 (CET) In-Reply-To: <20080102184957.GB2007@sirena.org.uk> 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 , Timur Tabi , linuxppc-dev@ozlabs.org, alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org Mark Brown wrote: > The machine support code (fabric driver in PowerPC terms, I think?) > tells the core how everything is connected together by registering > devices representing the links (eg, I2S) between the codecs, CPU and > other devices. The ASoC core is then responsible for ensuring that all > the required components are present before it registers with the ALSA > core. I'm no expert on this, but I think from the PowerPC point-of-view, the *ideal* situation would be if the ASoC fabric driver were generic, maybe even part of ASoC itself, and everything it needed could be obtained from the device tree. -- Timur Tabi Linux Kernel Developer @ Freescale From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from az33egw02.freescale.net (az33egw02.freescale.net [192.88.158.103]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "az33egw02.freescale.net", Issuer "Thawte Premium Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTP id CD56CDDF39 for ; Fri, 4 Jan 2008 05:15:21 +1100 (EST) Message-ID: <477D2673.5090203@freescale.com> Date: Thu, 03 Jan 2008 12:16:19 -0600 From: Timur Tabi MIME-Version: 1.0 To: Grant Likely , Timur Tabi , linuxppc-dev@ozlabs.org, alsa-devel@alsa-project.org Subject: Re: [alsa-devel] [PATCH] ASoC drivers for the Freescale MPC8610 SoC References: <11981089894052-git-send-email-timur@freescale.com> <9e4733910801012027p4be16b92r43af773f4e5ae531@mail.gmail.com> <477BADF5.9060003@freescale.com> <20080102184957.GB2007@sirena.org.uk> In-Reply-To: <20080102184957.GB2007@sirena.org.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Mark Brown wrote: > The machine support code (fabric driver in PowerPC terms, I think?) > tells the core how everything is connected together by registering > devices representing the links (eg, I2S) between the codecs, CPU and > other devices. The ASoC core is then responsible for ensuring that all > the required components are present before it registers with the ALSA > core. I'm no expert on this, but I think from the PowerPC point-of-view, the *ideal* situation would be if the ASoC fabric driver were generic, maybe even part of ASoC itself, and everything it needed could be obtained from the device tree. -- Timur Tabi Linux Kernel Developer @ Freescale