Skip to contentSkip to conversation

Store codec capabilites in alsa

DISCUSSION Bharath Ramachandramurthy 4 participants 8 messages Oct 26, 2012 – Oct 30, 2012

lore
Share & tools
lore
#0 lore raw

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

#1 lore raw
Quoted 8 lines · Bharath Ramachandramurthy

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.

Quoted 5 lines

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

#2 lore raw

On 10/26/2012 3:45 AM, Liam Girdwood wrote:
Hi Liam,

Quoted 1 line

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

Quoted 19 lines
Quoted 7 lines

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
[email protected]
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

Signature · 2 lines
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
#3 lore raw
Quoted 3 lines · Patrick Lai

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.

#4 lore raw
Quoted 8 lines · Mark Brown
Quoted 3 lines · Patrick Lai

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

Quoted 2 lines

than device specific.

Signature · 2 lines
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
#5 lore raw
Quoted 9 lines · Patrick Lai
Quoted 2 lines · Mark Brown

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.

#6 lore raw
Quoted 6 lines · Mark Brown
Quoted 4 lines · Patrick Lai
Quoted 2 lines · Mark Brown

Unless you tell us something about what's being advertised it's very hard to comment;

Quoted 9 lines
Quoted 4 lines

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.

Quoted 7 lines

_______________________________________________
Alsa-devel mailing list
[email protected]
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

Signature · 2 lines
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
#7 lore raw
Quoted 3 lines · Patrick Lai

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?