summaryrefslogtreecommitdiffstats
path: root/include/sound
diff options
context:
space:
mode:
authorTakashi Iwai <tiwai@suse.de>2012-03-09 17:51:10 +0100
committerTakashi Iwai <tiwai@suse.de>2012-03-09 17:55:30 +0100
commit18478e8b626edc2d181dcb1b93e1f99ad72095e9 (patch)
tree572587c5e3ce39669e4dff26b165e93ba3181946 /include/sound
parent785f857d1cb0856b612b46a0545b74aa2596e44a (diff)
downloadblackbird-obmc-linux-18478e8b626edc2d181dcb1b93e1f99ad72095e9.tar.gz
blackbird-obmc-linux-18478e8b626edc2d181dcb1b93e1f99ad72095e9.zip
ALSA: hda - Initialize vmaster slave volumes
When the driver is changed to use vmaster or a new slave element is added by the improvement of the parser code, user may face often the silent output because of the muted slave mixer although Master volume is properly set. And they complain. And I get upset. Although such a mixer element should be initialized via "alsactl init", it'd be more user-friendly if the known output slaves are unmuted and set to 0dB so that user can control the volume only with Master as default. Since Master is still set muted as default even with this change, no risk of the speaker blow up, too. Signed-off-by: Takashi Iwai <tiwai@suse.de>
Diffstat (limited to 'include/sound')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud