Mark Brown <broonie@xxxxxxxxxxxxx> writes: > On Thu, Mar 19, 2009 at 10:38:03AM -0700, Kevin Hilman wrote: > >> CLK(NULL, "mcasp0" &mcasp0_clk), >> CLK(NULL, "mcasp1", &mcasp1_clk), > > Exactly. > >> The platform code can do a clk_get(<physcial name>) and pass that >> clk in with the platform data. > > There should be no need to do this - the McASP DAI driver can just be a > regular platform device, probe as normal and register the DAI with the > ASoC core once it has done so. This is, in fact, the preferred method > for doing this though support for htis is recent so only one CPU DAI > driver does it so far. Sure, but what I don't want in that DAI driver is conditional code because of different clock names on different chips. For example, some devices may only have one clk, so the hardware name is actualy "mcasp" instead of "mcasp0" etc. IOW, there will always be conditional code, I would prefer it not to be in sound/soc/* and rather see it in the chip/board specific init code. Kevin _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
