[alsa-devel] Thoughts on ASOC v2 driver architecture

Mark Brown broonie at opensource.wolfsonmicro.com
Mon Jun 16 17:03:38 CEST 2008

On Mon, Jun 16, 2008 at 10:32:37AM -0400, Jon Smirl wrote:
> On 6/16/08, Timur Tabi <timur at freescale.com> wrote:
> > Jon Smirl wrote:

> > > I'd like for the fabric driver to be dynamically loaded by the device
> > tree.

> >  You have a PPC problem, not an ASoC problem.  You're trying to use the
> > device tree to load a device without specifying a specific node.  This is


> I think I've come up with a solution. Push all of that generic setup
> code in mpc8610_hpcd into fsl_ssi. Leave only the platform specific
> support in mpc8610_hpcd. Now turn mpc8610_hpcd into a loadable module
> but leave it as a platform_driver. During the fsl_ssi probe function
> extract the platform name from the device tree and use it to
> dynamically load the mpc8610_hpcd driver.

That should work from an ASoC point of view.

As Timur says, this is a PowerPC-specific problem - ASoC v2 itself
doesn't care how the various devices get instantiated.  The fabric,
codec and SoC drivers can all come up in any order and the core will
sort things out.

OOI, I guess that if there were some visible control on the board (eg, a
few controls via GPIO) then this would be less of an issue since there
would be real hardware for the machine/fabric driver to control?

More information about the Alsa-devel mailing list