Hi, On Sat, Jul 2, 2016 at 12:11 AM, Mark Brown <broonie@xxxxxxxxxx> wrote: > On Fri, Jul 01, 2016 at 10:49:46AM +0800, Garlic Tseng wrote: >> On Thu, 2016-06-30 at 20:55 +0800, Garlic Tseng wrote: > >> > If you worry about some potential risk (I don't see any) maybe we have >> > to develop another dummy bt-sco codec driver which support both 8k and >> > 16k? > >> Ah! If someone whose bluetooth modules only support 8k use the driver, >> they might be broken, right? Maybe we can add another snd_soc_dai_driver >> which can support both 8k and 16k. >> (Actually I found the issue is discussed before >> http://mailman.alsa-project.org/pipermail/alsa-devel/2014-November/084687.html ) > > Yes, that'd be fine - it could be the same driver and register different > parameters depending on config/compatible. Could we also make this driver directly configurable from Kconfig, and not just selected by platforms (currently Samsung) or by building all coddecs? Thanks ChenYu _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
