<p><br>
> ><br>
> > You have not posted alsa-info of working 3.18<br>
> ><br>
><br>
> Here are alsa-info.sh reports for both kernels:<br>
><br>
> <a href="http://misc.postpro.net/t510led/alsa_info_3.18.6.txt"> http://misc.postpro.net/t510led/alsa_info_3.18.6.txt</a><br>
> <a href="http://misc.postpro.net/t510led/alsa_info_3.19.3_soft0.txt"> http://misc.postpro.net/t510led/alsa_info_3.19.3_soft0.txt</a><br>
> <a href="http://misc.postpro.net/t510led/alsa_info_3.19.3_soft1.txt"> http://misc.postpro.net/t510led/alsa_info_3.19.3_soft1.txt</a><br>
><br>
> The difference between the 3.19 "soft0" and "soft1" versions is that "soft0"<br>
> version was booted with the kernel commandline parameter<br>
><br>
> thinkpad_acpi.software_mute=0<br>
><br>
> This just reverts the muting behavior back to 3.18 (which is my preference).<br>
> The "soft1" version does not supply this parameter, so you get the default<br>
> 3.19 behavior (i.e., software muting enabled, HW muting disabled.)<br>
><br>
><br>
> ><br>
> > Refer to alsa-info found in t510 speaker powersave regression<br>
> ><br>
> ><a href="https://lkml.org/lkml/2012/12/22/113"> https://lkml.org/lkml/2012/12/22/113</a><br>
> ><br>
><br>
> Superficially, to my eyes anyway, it doesn't seem related to this issue.<br>
> Do you think it might be? If so, please be more explicit, I don't see<br>
> the connection.<br>
><br>
> ><br>
> > Simple mixer control 'Console',0<br>
> > Capabilities: pswitch pswitch-joined<br>
> > Playback channels: Mono<br>
> Mono: Playback [on]<br>
> ><br>
> > Do this console playback switch has any effect on your schematic view ?<br>
> ><br>
><br>
> It's a read-only card, so it has no "effect", but its state does reflect<br>
> the HW mute state. See further below for details.<br>
><br>
> ><br>
> > AFAIK, pulseaudio ignore card 29 "ThinkPadEC"<br>
> ><br>
><br>
> Yes, that seems to be right. But it can be seen via amixer -c29: Here's the<br>
> observed behavior under 3.18, using the terminology from the kernel bug<br>
> report:<br>
><br>
> 0. Toggle MUTEKEY until MUTELED = off.<br>
> 1. Start audio source, verify SPK_SOUND = on<br>
> 2. 'amixer -c29 get Console' reports "Mono: Playback [on]"<br>
> 3. Toggle MUTEKEY, verify MUTELED = on, SPK_SOUND = off<br>
> 4. 'amixer -c29 get Console' reports "Mono: Playback [off]"<br>
><br>
> That's all I see.</p>
<p>Refer to</p>
<p><a href="http://www.spinics.net/lists/ibm-acpi-devel/msg03404.html">http://www.spinics.net/lists/ibm-acpi-devel/msg03404.html</a></p>
<p>Starting with 3.19, the default behavior is to ask the embedded<br>
controller to disable all the magic. The kernel will keep the mute<br>
LED in sync with the software control, the hardware switch is disabled entirely, and the mute button is just a button.</p>
<p>This mean the function of mute key is disabled by default</p>
<p><a href="http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/platform/x86/thinkpad_acpi.c?id=9a417ec0c9d1f7af5394333411fc4d98adb8761b">http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/platform/x86/thinkpad_acpi.c?id=9a417ec0c9d1f7af5394333411fc4d98adb8761b</a></p>
<p>Speaker still follow pin sense of hp and dock hp of hda codec when auto mute mode is enabled</p>
<p>Simple mixer control 'Auto-Mute Mode',0<br>
Capabilities: enum<br>
Items: 'Disabled' 'Enabled'<br>
Item0: 'Enabled'</p>
<p>You need to find out how to listen mute key event<br></p>