On Thu, 25 Sep 2008 10:41:48 -0700 "ext David Brownell" <david-b@xxxxxxxxxxx> wrote: > > Putting the board specific bits in the > > arch/arm/mach-omap2/board-XYZ.c file has been discussed a number of > > times on alsa-devel and the folks there insist that for now (i.e. > > ASoC V1) this is the proper way to do things. > > Hmm, I'm not sure I follow. They want the SOC devices > in the wrong place in the driver model tree, potentially > impacting power management? > > I don't want to fight that fight, but ... that seems unwise. > Yep. Now in ASoC v1, the machine, platform/CPU and codec are tied together during compile time and I think it has been easier to review/manage by keeping them under one sound/soc directory. I suppose that when ASoC v2 is in place and devices can be individually probed, we might see that machine drivers will start moving out from there. Jarkko -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
