On Mon, Feb 01, 2010 at 04:20:38PM +0100, Richard Röjfors wrote: > Mark Brown wrote: > > Without having investigated in any great detail I'd really expect this > > driver to be done within ASoC if it's producing generic I2S output. If > > it's producing I2S out then presumably system designers will be able to > > attach whatever CODECs they desire and if those CODECs require any soft > > control then there will be a need to interoperate with CODEC drivers. > This thing produces raw I2S/captures raw I2S as you say. It's used to > connect to bluetooth chips and radio DSP:s. So there are no CODEC:s > involved. Does it make sense to do it within ASoC? Presumably there's nothing intrinsic in the hardware which makes this specific to bluetooth and other radios? If it's just vanilla I2S out I'd be shocked if nobody ever decided to hook it up to a CODEC for some reason or other, even if that CODEC is just being used to hook up to an analogue baseband that's been selected for some reason. In any case, due to mobile phones things like the bluetooth are getting represented in ASoC and it's trivial to provide a stub for them where they aren't so it seems sensible to have the option to hook the device up in ASoC. _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
