[alsa-devel] Can we remove the rtd_aux for the aux_devs?
Mengdong Lin
mengdong.lin at linux.intel.com
Tue Dec 22 09:15:26 CET 2015
Revise the subject.
Could someone clarify if the rtd_aux in struct snd_soc_card is still needed?
We want to replace the aux_dev by aux_component.
If the rtd_aux is no longer needed, we can remove the array and it will
become easier to handle an aux_dev as a generic component.
Thanks
Mengdong
On 12/16/2015 04:33 PM, Mengdong Lin wrote:
>
>
> On 12/15/2015 07:23 PM, Mark Brown wrote:
>> On Tue, Dec 15, 2015 at 04:06:14PM +0800, Mengdong Lin wrote:
>>
>>> I still have some basic questions:
>>
>>> 1. What are the typical usages for aux_dev?
>>> For CODEC<->CODEC link or external headset detection chip?
>>
>> Neither, it's for analogue devices.
>
> Got it. Thanks!
>
>>
>>> 2. Why we need the rtd array 'rtd_aux' for the aux_devs?
>>> If the codec has DAIs and used by a DAI link, the ASoC will
>>> create a rtd
>>> for the link.
>>
>> There are (or were at the time) assumptions in drivers that there will
>> be a rtd there so it was easier to provide a stub.
>>
>
> Can we remove this rtd array if current driver does not need the stub?
>
> For the replacement of aux_dev by aux_component, can we define like below?
>
> struct snd_soc_aux_component {
> const char *comp_name; ... no longer assume they're only codecs
> const char *comp_of_node;
>
> /* machine specific init */
> int (*init)(struct snd_soc_component *componnent);
> };
>
> The ASoC can use the comp_name or comp_of_node to find the components
> and probe them.
>
> Thanks
> Mengdong
>
More information about the Alsa-devel
mailing list