[alsa-devel] ASUS T100TAM UCM

Michal Feix michal at feix.family
Mon Jan 27 10:32:58 CET 2020


Dne 27. 01. 20 v 9:21 Jaroslav Kysela napsal(a):
> Dne 23. 01. 20 v 15:20 Michal Feix napsal(a):
>>> Dne 23. 01. 20 v 15:10 Michal Feix napsal(a):
>>>>> On 1/23/20 6:49 AM, Michal Feix wrote:
>>>>>> Hello,
>>>>>>
>>>>>> there is no sound working via speakers or headphones jack on Asus T100TAM. Sound works correctly via HDMI or Bluetooth headphones. The chip on this Baytrail machine is correctly recognized as bytcr_rt5640.  From dmesg:
>>>>>>
>>>>>> bytcr_rt5640 bytcr_rt5640: quirk DMIC1_MAP enabled
>>>>>> bytcr_rt5640 bytcr_rt5640: quirk realtek,jack-detect-source 3
>>>>>> bytcr_rt5640 bytcr_rt5640: quirk realtek,over-current-threshold-microamp 2000
>>>>>> bytcr_rt5640 bytcr_rt5640: quirk realtek,over-current-scale-factor 1
>>>>>> bytcr_rt5640 bytcr_rt5640: quirk MCLK_EN enabled
>>>>>> bytcr_rt5640 bytcr_rt5640: snd-soc-dummy-dai <-> media-cpu-dai mapping ok
>>>>>> bytcr_rt5640 bytcr_rt5640: snd-soc-dummy-dai <-> deepbuffer-cpu-dai mapping ok
>>>>>> bytcr_rt5640 bytcr_rt5640: rt5640-aif1 <-> ssp2-port mapping ok
>>>>>> input: bytcr-rt5640 Headset as /devices/platform/80860F28:00/bytcr_rt5640/sound/card0/input17
>>>>>>
>>>>>> After bootup, kernel log is filled with: "Baytrail Audio Port: ASoC: no backend DAIs enabled for Baytrail Audio Port" messages. I do understand this is due to the missing UCM profile for the machine.
>>>>>
>>>>> what do you mean with 'missing UCM profile'? It's been available for many moons, and we worked with Jaroslav/Hans to update for UCMv2.
>>>>>
>>>>> You should be able to use alsa-ucm and configure things manually, e.g.
>>>>>
>>>>> alsaucm -c bytcr-rt5640 set _verb HiFi set _enadev Headphones
>>>>>
>>>>> alsaucm -c bytcr-rt5640 set _verb HiFi set _enadev Speaker
>>>>>
>>>>
>>>> Thanks Pierre. I'm aware of the work done previously on Asus T100. Not sure, if Asus T100TAM is any significantly different. Just tried your suggested commands as root user:
>>>>
>>>> # alsaucm -c bytcr-rt5640 set _verb HiFi set _enadev Headphones
>>>> ALSA lib ucm_subs.c:215:(uc_mgr_get_substituted_value) variable '${CardComponents}' is not defined in this context!
>>>> ALSA lib main.c:960:(snd_use_case_mgr_open) error: failed to import bytcr-rt5640 use case configuration -22
>>>> alsaucm: error failed to open sound card bytcr-rt5640: Invalid argument
>>>>
>>>> # alsaucm -c bytcr-rt5640 set _verb HiFi set _enadev Speaker
>>>> ALSA lib ucm_subs.c:215:(uc_mgr_get_substituted_value) variable '${CardComponents}' is not defined in this context!
>>>> ALSA lib main.c:960:(snd_use_case_mgr_open) error: failed to import bytcr-rt5640 use case configuration -22
>>>> alsaucm: error failed to open sound card bytcr-rt5640: Invalid argument
>>>
>>> Try this:
>>>
>>> alsaucm -c hw:0 set _verb HiFi set _enadev Speaker
>>>
>>>                   Thank you,
>>>                       Jaroslav
>>>
>>
>> No luck.
>>
>> # alsaucm -c hw:0 set _verb HiFi set _enadev Speaker
>> ALSA lib ucm_subs.c:215:(uc_mgr_get_substituted_value) variable '${CardComponents}' is not defined in this context!
>> ALSA lib main.c:960:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -22
>> alsaucm: error failed to open sound card hw:0: Invalid argument
> 
> I think that this issue is fixed in the not-yet-released code in alsa-lib.

Does that mean that by fixing "this issue" alsaucm should be able to correctly load the UCM2 profile on this Asus device? Or is this fix supposed to make alsaucm showing something more reasonable?

On my other machine with different sound card (HDA Intel PCH) "alsaucm listcards" is also showing the same error, but sound is working perfectly.

--
Michal


More information about the Alsa-devel mailing list