unicens 4a-HAL leaves some required control at value Zero (muted) at each boot

Description

Critical controls (Fallback_Ramp & Master_Ramp) are set to naught (0) at each boot by the 4a unicens hal.

So there is no sound coming out of the card (muted).

$ amixer -D hw:ep016ch cset name='Fallback_Ramp' 100

$ amixer -D hw:ep016ch cset name='Master_Ramp' 100

$ speaker-test -D Emergency -c 6 -t wav

Environment

None

Activity

Tobias Jahnke 
December 20, 2017 at 7:29 PM

This issue seems to be fixed completely in eel. Chris came up with an eel image. All volume controls are up as expected.

Please give feedback if you still see an issue in eel.

Tobias Jahnke 
December 20, 2017 at 10:49 AM

Master volume is fixed by the following patch:

https://gerrit.automotivelinux.org/gerrit/#/c/12803/

However, this does not fix the entire issue in general which seems to be timing/dependency related.

Tobias Jahnke 
December 20, 2017 at 9:48 AM

I've seen a similar issue after the first boot of an image from yesterday's "master".

It seems that the initial value is missing for Master_Ramp. Patch should be simple if this is the cause.

I will see if it's reproducible in my dev environment and fix.

Dominig ar Foll 
December 19, 2017 at 10:20 AM

I checked what is the result after a manual load.

Fallback-ramp is setup to valid value but master-ramp remains to naught (0).

When it come to the sequence, I have noticed that you have no dependency on waiting that your init service is terminated before going on with the initialization.  

No services waits for /lib/systemd/system/unicens-config.service, so if CPU is fast and multitheaded it will fail.

see https://lf-automotivelinux.atlassian.net/browse/SPEC-1204

Tobias Jahnke 
December 19, 2017 at 9:52 AM

4a-hal-unicens needs:

  • MOST driver must be loaded

  • /usr/bin/unicens-config.sh must be finished
    There is a fix pending (Soya-San found), but it is only related to UnshieldedTwistedPair(UTP)-Setup

  • require alsa-core (for HalServiceInit()) 

  • requires API "agl-service-unicens" started (setting up the network)

That should be the current order as it is currently implemented. I can try to change the last 2 ones.

 

Besides that. Is the there be an issue with privileges or is there an audio group, which may have an impact during boot? 

 

Fixed

Details

Assignee

Reporter

Fix versions

Labels

Components

Priority

Created December 19, 2017 at 7:33 AM
Updated May 8, 2018 at 12:37 PM
Resolved April 30, 2018 at 11:48 AM