From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <9e4733910710241231h9427223kbfcc23be2e111194@mail.gmail.com> Date: Wed, 24 Oct 2007 15:31:09 -0400 From: "Jon Smirl" To: "Timur Tabi" Subject: Re: Audio codec device tree entries In-Reply-To: <471F7D28.6050107@freescale.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 References: <9e4733910710221859q6ea54810nba58907d5ddd966d@mail.gmail.com> <9e4733910710240800y24952e70g8c318e35e2e45e2e@mail.gmail.com> <9e4733910710240828x412f598dy7fc4a75faa76358d@mail.gmail.com> <9e4733910710240854y6ac115b6i5e0400eb369fcf7@mail.gmail.com> <9e4733910710241001g165e7aeatdc92096544fbeb60@mail.gmail.com> <471F7D28.6050107@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 10/24/07, Timur Tabi wrote: > Jon Smirl wrote: > > > Calling it directly from the platform code is an option, but where > > does the fabric driver code live? It doesn't make a lot of sense to > > put ALSA code into arch/powerpc/platforms/52xx. I could make a > > function call from arch/powerpc/platforms/52xx over to > > sound/soc/powerpc but that's not very pretty. > > sound/soc/fsl is where the non-codec ASoC drivers for Freescale parts should go. Why are you using a vendor named directory? I don't believe vendor named directories are used anywhere in the kernel. The directories are always named after the platform or architecture. Vendor directories end up in a big mess if Freescale decides to sell a CPU to someone else. > > > The codec drivers in asoc are completely agnostic. The same codec > > driver works on x86, arm, powerpc, etc. > > Well, in theory at least. I never tried my cs4270 driver on anything but PowerPC. > > -- Jon Smirl jonsmirl@gmail.com