From mboxrd@z Thu Jan 1 00:00:00 1970 From: Grant Likely Subject: Re: [PATCH v2 1/3] ALSA SoC: Add OpenFirmware helper for matching bus and codec drivers Date: Mon, 14 Jul 2008 16:28:08 -0600 Message-ID: <20080714222808.GA7073@secretlab.ca> References: <20080712083929.15025.47682.stgit@trillian.secretlab.ca> <20080714134930.GC25448@sirena.org.uk> <9e4733910807140713r5739efedw81e65632006d101d@mail.gmail.com> <20080714150527.GD25448@sirena.org.uk> <487B7B71.9060606@freescale.com> <20080714165302.GG25448@sirena.org.uk> <20080714183632.GI25448@sirena.org.uk> <487B9D98.8010008@freescale.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from yw-out-1718.google.com (yw-out-1718.google.com [74.125.46.153]) by alsa0.perex.cz (Postfix) with ESMTP id 4137B24426 for ; Tue, 15 Jul 2008 00:28:34 +0200 (CEST) Received: by yw-out-1718.google.com with SMTP id 9so2533696ywk.2 for ; Mon, 14 Jul 2008 15:28:11 -0700 (PDT) Content-Disposition: inline In-Reply-To: <487B9D98.8010008@freescale.com> 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: Timur Tabi Cc: linuxppc-dev@ozlabs.org, alsa-devel@alsa-project.org, liam.girdwood@wolfsonmicro.com List-Id: alsa-devel@alsa-project.org On Mon, Jul 14, 2008 at 01:40:24PM -0500, Timur Tabi wrote: > Mark Brown wrote: > > > Desktop Management Interface, a standard BIOS interface for getting > > system data on x86 class hardware. Of particular interest here is the > > fact that it contains various ID strings for things like motherboard and > > chassis - on Linux drivers can be automatically loaded based on these > > strings. See drivers/misc/thinkpad_acpi.c for an example of a driver > > that does this. > > The only problem with this is that the OF probing code in the kernel binds > drivers to device tree nodes. So when a driver claims a node, no other driver > will be probed with it. Yes, but that is only for the of_platform bus which is just one way to setup device drivers from the device tree. Setting it up from the platform code is just as valid an option. Or, each ASoC machine driver could read the device tree itself in the module_init hook to decide whether or not to instantiate itself. Cheers, g. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.173]) by ozlabs.org (Postfix) with ESMTP id 8529BDDE00 for ; Tue, 15 Jul 2008 08:28:12 +1000 (EST) Received: by wf-out-1314.google.com with SMTP id 24so4861829wfg.15 for ; Mon, 14 Jul 2008 15:28:10 -0700 (PDT) Date: Mon, 14 Jul 2008 16:28:08 -0600 From: Grant Likely To: Timur Tabi Subject: Re: [alsa-devel] [PATCH v2 1/3] ALSA SoC: Add OpenFirmware helper for matching bus and codec drivers Message-ID: <20080714222808.GA7073@secretlab.ca> References: <20080712083929.15025.47682.stgit@trillian.secretlab.ca> <20080714134930.GC25448@sirena.org.uk> <9e4733910807140713r5739efedw81e65632006d101d@mail.gmail.com> <20080714150527.GD25448@sirena.org.uk> <487B7B71.9060606@freescale.com> <20080714165302.GG25448@sirena.org.uk> <20080714183632.GI25448@sirena.org.uk> <487B9D98.8010008@freescale.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <487B9D98.8010008@freescale.com> Sender: Grant Likely Cc: linuxppc-dev@ozlabs.org, alsa-devel@alsa-project.org, liam.girdwood@wolfsonmicro.com List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, Jul 14, 2008 at 01:40:24PM -0500, Timur Tabi wrote: > Mark Brown wrote: > > > Desktop Management Interface, a standard BIOS interface for getting > > system data on x86 class hardware. Of particular interest here is the > > fact that it contains various ID strings for things like motherboard and > > chassis - on Linux drivers can be automatically loaded based on these > > strings. See drivers/misc/thinkpad_acpi.c for an example of a driver > > that does this. > > The only problem with this is that the OF probing code in the kernel binds > drivers to device tree nodes. So when a driver claims a node, no other driver > will be probed with it. Yes, but that is only for the of_platform bus which is just one way to setup device drivers from the device tree. Setting it up from the platform code is just as valid an option. Or, each ASoC machine driver could read the device tree itself in the module_init hook to decide whether or not to instantiate itself. Cheers, g.