On 10/30/2012 8:13 AM, Mark Brown wrote:
On Mon, Oct 29, 2012 at 08:23:28PM -0700, Patrick Lai wrote:
On 10/29/2012 10:07 AM, Mark Brown wrote:
Unless you tell us something about what's being advertised it's very hard to comment;
CODEC has filters for noise cancellation purpose. CPU will need to know given CODEC has noise cancellation support. Also, CPU needs to know the CODEC registers to program the filters and which digital audio interface would have noise reference.
Why is this all not just normal configuration done from the application layer? Especially the noise reference configuration just looks like totally normal routing configuration.
Agree that for noise reference can be done through normal routing configuration. However, CPU driver does not normally manage CODEC register. In my case, CPU algorithm module needs to know what CODEC registers to program in order to update the filters. So far, ASoC model has partitioned roles of CPU and CODEC to be managed by CPU driver and CODEC driver. Both drivers talk on common interface to allow easy swap out of CPU hardware or CODEC hardware. In our case, the requirement described so far requires tight coupling of CPU and CODEC. We are looking to maintain clean partition while meeting the requirement through ASoc framework.
Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel