This removes ambiguity on the mixer choice when 4A is enabled.
The warning seen at the beginning of bitbake also disappears:
------
NOTE: Multiple providers are available for runtime virtual/mixer (4a-mixer, mixer)
Consider defining a PREFERRED_RPROVIDER entry to match virtual/mixer
------
Bug-AGL: SPEC-1520
Change-Id: I2fb9173f4616dc3d26ce5bc11f1c1686179d0456
Signed-off-by: Stephane Desneux <stephane.desneux@iot.bzh>
PACKAGES_pn-alsa-state_remove = "alsa-states-dev"
PACKAGES_pn-alsa-state = "alsa-state alsa-states"
-PREFERRED_PROVIDER_virtual/mixer ?= "4a-mixer"
+PREFERRED_RPROVIDER_virtual/mixer ?= "4a-mixer"
PREFERRED_VERSION_alsa-lib = "1.1.6"
PREFERRED_VERSION_alsa-plugins = "1.1.6"