* Store codec capabilites in alsa @ 2012-10-26 2:07 Bharath Ramachandramurthy 2012-10-26 10:45 ` Liam Girdwood 0 siblings, 1 reply; 8+ messages in thread From: Bharath Ramachandramurthy @ 2012-10-26 2:07 UTC (permalink / raw) To: alsa-devel; +Cc: bramacha Hello Is there a mechanism for the codec driver to register the codec capabilities to the ALSA framework ? The BE CPU dai driver can then read the capabilities of the codec and talk to the DSP. Thanks Bharath ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Store codec capabilites in alsa 2012-10-26 2:07 Store codec capabilites in alsa Bharath Ramachandramurthy @ 2012-10-26 10:45 ` Liam Girdwood 2012-10-29 1:13 ` Patrick Lai 0 siblings, 1 reply; 8+ messages in thread From: Liam Girdwood @ 2012-10-26 10:45 UTC (permalink / raw) To: alsa-devel; +Cc: Mark Brown On 26/10/12 03:07, Bharath Ramachandramurthy wrote: > Hello > > > > Is there a mechanism for the codec driver to register the codec > capabilities to the ALSA framework ? > > The codec DAI driver does register some of it's capabilities with the core. > > The BE CPU dai driver can then read the capabilities of the codec and talk > to the DSP. > > You should be able to do this by looking at the RTD codec->driver pointer to get supported rates, formats and channels. Regards Liam ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Store codec capabilites in alsa 2012-10-26 10:45 ` Liam Girdwood @ 2012-10-29 1:13 ` Patrick Lai 2012-10-29 17:07 ` Mark Brown 0 siblings, 1 reply; 8+ messages in thread From: Patrick Lai @ 2012-10-29 1:13 UTC (permalink / raw) To: Liam Girdwood; +Cc: alsa-devel, Mark Brown On 10/26/2012 3:45 AM, Liam Girdwood wrote: Hi Liam, > The codec DAI driver does register some of it's capabilities with the core. The CODEC Bharath and I are working with has hardware providing information back to CPU so post processing modules running on CPU can fine tune things on the CODEC continuously. So, the information need to exposed to CPU is more than supported rates, format, and channels but very CODEC specific. I doubt that ASoC has mechanism for vendor's own CODEC driver to advertise CODEC specific information. However, we would like to check ahead of time before coming up with something on our own. Thanks Patrick > > >> >> The BE CPU dai driver can then read the capabilities of the codec and talk >> to the DSP. >> >> > > You should be able to do this by looking at the RTD codec->driver pointer to get supported rates, formats and channels. > > Regards > > Liam > > _______________________________________________ > Alsa-devel mailing list > Alsa-devel@alsa-project.org > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel > -- Sent by an employee of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum. ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Store codec capabilites in alsa 2012-10-29 1:13 ` Patrick Lai @ 2012-10-29 17:07 ` Mark Brown 2012-10-30 3:23 ` Patrick Lai 0 siblings, 1 reply; 8+ messages in thread From: Mark Brown @ 2012-10-29 17:07 UTC (permalink / raw) To: Patrick Lai; +Cc: alsa-devel, Liam Girdwood [-- Attachment #1.1: Type: text/plain, Size: 422 bytes --] On Sun, Oct 28, 2012 at 06:13:08PM -0700, Patrick Lai wrote: > I doubt that ASoC has mechanism for vendor's own CODEC driver to > advertise CODEC specific information. However, we would like to > check ahead of time before coming up with something on our own. Unless you tell us something about what's being advertised it's very hard to comment; it's often the case that things are just new rather than device specific. [-- Attachment #1.2: Digital signature --] [-- Type: application/pgp-signature, Size: 836 bytes --] [-- Attachment #2: Type: text/plain, Size: 0 bytes --] ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Store codec capabilites in alsa 2012-10-29 17:07 ` Mark Brown @ 2012-10-30 3:23 ` Patrick Lai 2012-10-30 15:13 ` Mark Brown 0 siblings, 1 reply; 8+ messages in thread From: Patrick Lai @ 2012-10-30 3:23 UTC (permalink / raw) To: Mark Brown; +Cc: alsa-devel, Liam Girdwood On 10/29/2012 10:07 AM, Mark Brown wrote: > On Sun, Oct 28, 2012 at 06:13:08PM -0700, Patrick Lai wrote: > >> I doubt that ASoC has mechanism for vendor's own CODEC driver to >> advertise CODEC specific information. However, we would like to >> check ahead of time before coming up with something on our own. > > 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. Thanks Patrick it's often the case that things are just new rather > than device specific. > -- Sent by an employee of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum. ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Store codec capabilites in alsa 2012-10-30 3:23 ` Patrick Lai @ 2012-10-30 15:13 ` Mark Brown 2012-10-30 18:18 ` Patrick Lai 0 siblings, 1 reply; 8+ messages in thread From: Mark Brown @ 2012-10-30 15:13 UTC (permalink / raw) To: Patrick Lai; +Cc: alsa-devel, Liam Girdwood [-- Attachment #1.1: Type: text/plain, Size: 632 bytes --] 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. [-- Attachment #1.2: Digital signature --] [-- Type: application/pgp-signature, Size: 836 bytes --] [-- Attachment #2: Type: text/plain, Size: 0 bytes --] ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Store codec capabilites in alsa 2012-10-30 15:13 ` Mark Brown @ 2012-10-30 18:18 ` Patrick Lai 2012-10-30 18:42 ` Mark Brown 0 siblings, 1 reply; 8+ messages in thread From: Patrick Lai @ 2012-10-30 18:18 UTC (permalink / raw) To: Mark Brown; +Cc: alsa-devel, Liam Girdwood 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 > -- Sent by an employee of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum. ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Store codec capabilites in alsa 2012-10-30 18:18 ` Patrick Lai @ 2012-10-30 18:42 ` Mark Brown 0 siblings, 0 replies; 8+ messages in thread From: Mark Brown @ 2012-10-30 18:42 UTC (permalink / raw) To: Patrick Lai; +Cc: alsa-devel, Liam Girdwood [-- Attachment #1.1: Type: text/plain, Size: 353 bytes --] On Tue, Oct 30, 2012 at 11:18:57AM -0700, Patrick Lai wrote: > 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. Why does the CPU driver want to update the filters in the CODEC? Can't the application do this? [-- Attachment #1.2: Digital signature --] [-- Type: application/pgp-signature, Size: 836 bytes --] [-- Attachment #2: Type: text/plain, Size: 0 bytes --] ^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2012-10-30 18:42 UTC | newest] Thread overview: 8+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2012-10-26 2:07 Store codec capabilites in alsa Bharath Ramachandramurthy 2012-10-26 10:45 ` Liam Girdwood 2012-10-29 1:13 ` Patrick Lai 2012-10-29 17:07 ` Mark Brown 2012-10-30 3:23 ` Patrick Lai 2012-10-30 15:13 ` Mark Brown 2012-10-30 18:18 ` Patrick Lai 2012-10-30 18:42 ` Mark Brown
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).