[alsa-devel] auto_mute for early patch issue

Kailang kailang at realtek.com
Thu Jan 31 05:08:05 CET 2019


Hi Takashi,

Chrome OS use early patch firmware file to load model and use auto_mute =no hint options.
I find an issue for early patch issue about hint option auto_mute = no.

This will cause all spec->init_hook can't get hp_pin values.

For example: alc225_init() alc225_shutup() alc256_init() alc256_shutup()
Early patch file hint auto_mute = no equal spec->suppress_auto_mute = 1
It will return function check_auto_mute_availability() in had_generic.c.

hp_pin = spec->gen.autocfg.hp_pins[0];  ==> It will get value 0.

I think this issue was for a long time.
Please see the attach dmesg. One is kill hint auto_mute option. 

BR,
Kailang

-------------- next part --------------
A non-text attachment was scrubbed...
Name: hp_pin.dmesg_kill_auto_mute
Type: application/octet-stream
Size: 3061 bytes
Desc: hp_pin.dmesg_kill_auto_mute
URL: <http://mailman.alsa-project.org/pipermail/alsa-devel/attachments/20190131/6a294756/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: hp_pin.dmesg_with_auto_mute_no
Type: application/octet-stream
Size: 3015 bytes
Desc: hp_pin.dmesg_with_auto_mute_no
URL: <http://mailman.alsa-project.org/pipermail/alsa-devel/attachments/20190131/6a294756/attachment-0003.obj>


More information about the Alsa-devel mailing list