From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <9e4733910711260838s26e5b155n8d1cb2c246248394@mail.gmail.com> Date: Mon, 26 Nov 2007 11:38:44 -0500 From: "Jon Smirl" To: "Timur Tabi" Subject: Re: Revisited, audio codec device tree entries. In-Reply-To: <474AEB6A.40408@freescale.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 References: <9e4733910711181010q50c08d2ek8413af74d58cf0ce@mail.gmail.com> <9e4733910711190800t5dc9bc40q1b58feae4ff364d0@mail.gmail.com> <9e4733910711190851g3e1f2ef9k5f87c7c2dae929ef@mail.gmail.com> <9e4733910711191120l45d9257bwf4ccf8c7365393d0@mail.gmail.com> <20071120005941.GC3126@localhost.localdomain> <474AEB6A.40408@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 11/26/07, Timur Tabi wrote: > David Gibson wrote: > > > 1) We have a "universal" device-tree-based fabric driver which > > parses all the above-described interconnection information in the > > device tree and handles any situation. Cool, but probably a lot of > > work and fiddly to get right. > > Definitely a lot of work. I suggest we wait until there are a few PowerPC ASOC > v2 audio drivers in the kernel before we even consider this. And it may not > even be possible. I can easily imagine situations where we need board-specific > code that belongs in a machine-specific fabric driver. I'm fixing up the asoc v2 code to use MODULE_DEVICE_TABLE() and the real kernel aliasing/insmod system. Half of why we are having trouble is because asoc isn't using this mechanism. I've posted patches fixing i2c to use the same mechanism. I don't have the asoc ones ready yet. > > -- > Timur Tabi > Linux kernel developer at Freescale > -- Jon Smirl jonsmirl@gmail.com