From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.185]) by ozlabs.org (Postfix) with ESMTP id 03EA0DDEDD for ; Thu, 3 Jan 2008 05:43:49 +1100 (EST) Received: by rv-out-0910.google.com with SMTP id c27so3898009rvf.9 for ; Wed, 02 Jan 2008 10:43:46 -0800 (PST) Message-ID: <9e4733910801021043l7571ea00o7b8072b04ca68ad5@mail.gmail.com> Date: Wed, 2 Jan 2008 13:43:46 -0500 From: "Jon Smirl" To: "Grant Likely" Subject: Re: [PATCH] ASoC drivers for the Freescale MPC8610 SoC In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 References: <11981089894052-git-send-email-timur@freescale.com> <9e4733910801012027p4be16b92r43af773f4e5ae531@mail.gmail.com> <477BADF5.9060003@freescale.com> <9e4733910801020756p18e12ce8o618b8eae5e7c5a53@mail.gmail.com> <9e4733910801020912k50dceaebm11b59c1cee571e56@mail.gmail.com> Cc: linuxppc-dev@ozlabs.org, alsa-devel@alsa-project.org, Timur Tabi List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 1/2/08, Grant Likely wrote: > > Alternatively, the best place for this device would be on the ASOC > > bus, but the ASOC bus hasn't been created when the platform code runs. > > Maybe I can figure out a place in the platform code to create this > > device after the ASOC driver has loaded and created the bus. Does the > > platform code get control back after loading all of the device > > drivers? > > Yes, but it requires the core ASoC code to not be a module. Then you > can use machine_device_initcall() to register the device at a later > time. How about this for a simpler solution? My mpc5200-psc-ac97 and mpc5200-psc-i2c drivers can create a device on the ASOC bus named after the first entry in the compatible field of the root node. That will cause the correct driver to get activated. I'm in the process of making ASOC drivers dynamically loadable like the i2c ones. -- Jon Smirl jonsmirl@gmail.com