From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <9e4733910710211512v238fbc89m35783d5eb5b82bf6@mail.gmail.com> Date: Sun, 21 Oct 2007 18:12:41 -0400 From: "Jon Smirl" To: benh@kernel.crashing.org Subject: Re: Device trees and audio codecs In-Reply-To: <1193004399.6745.39.camel@pasglop> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 References: <9e4733910710200833x5d1c55b5l2cd400f77c13ec87@mail.gmail.com> <9e4733910710211433r7e0cf4b4sf6aed12c57dda375@mail.gmail.com> <1193004399.6745.39.camel@pasglop> Cc: PowerPC dev list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 10/21/07, Benjamin Herrenschmidt wrote: > > On Sun, 2007-10-21 at 17:33 -0400, Jon Smirl wrote: > > > This is one of the i2s channels on the macio. Dunno why they put > > > all those platform-XXX entries in here, (most of) these don't > > > logically belong here. > > > > Actually those platform-XXX entries may be the solution I am looking > > for. I can use the generic i2s driver to load a fabric driver as an > > ALSA module. > > Yuck. And your alternative is? I can use the DTC to load the I2S and codec drivers. How do I get the platform specific fabric driver loaded? There is no way to load a driver matching on the platform name. -- Jon Smirl jonsmirl@gmail.com