All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hui Wang <hui.wang@canonical.com>
To: Raymond Yau <superquad.vortex2@gmail.com>,
	Jan Kiszka <jan.kiszka@web.de>
Cc: ALSA Development Mailing List <alsa-devel@alsa-project.org>,
	Hui Wang <jason77.wang@gmail.com>,
	tiwai@suse.de,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	alex.hung@canonical.com, david.henningsson@canonical.com
Subject: Re: [alsa-devel] [V2 PATCH] ALSA: hda - Enable mute/mic-mute LEDs for more Thinkpads with Conexant codec
Date: Wed, 01 Jul 2015 17:51:20 +0800	[thread overview]
Message-ID: <5593B818.2060405@canonical.com> (raw)
In-Reply-To: <55909630.9060704@canonical.com>

On 06/29/2015 08:49 AM, Hui Wang wrote:
> On 06/27/2015 11:03 AM, Raymond Yau wrote:
>>>>>>>>>>>>>> Most Thinkpad Edge series laptops use conexant codec, so far
>>>>>>>>>>>>>> although
>>>>>>>> <snip>
>>>>>>>>>>> Is there anything I can debug or any information I can collect
>>>>>>>>>>> from my
>>>>>>>>>>> box to examine this?
>>>>>>>>>> What is the linux distribution on your machine? And use 
>>>>>>>>>> showkey to
>>>>>>>>>> catch
>>>>>>>>>> the keycode of that button.
>>>>>>>>> I'm running OpenSUSE 13.1. The reported keycode of the power
>>>>>>>>> button is
>>>>>>>>> 116.
>>>>>>>> It seems the keycode is correct, it is power keycode rather the 
>>>>>>>> mute
>>>>>>>> keycode.
>>>>>>>>
>>>>>>>> Could you please do some debug, let us find which line of code is
>> the
>>>>>>>> root cause for this problem. for example:
>>>>>>>>
>>>>>>>> after running the line, the problem shows up:
>>>>>>>>
>>>>>>>> 1.     if (ACPI_SUCCESS(acpi_get_devices("LEN0068", acpi_check_cb,
>>>>>>>> &found, NULL)) && found) // in the 
>>>>>>>> sound/pci/hda/thinkpad_helper.c,
>>>>>>>> is_thinkpad()
>>>>>>> This evaluates to true
>>>>>>>
>>>>>>>> 2.     return ACPI_SUCCESS(acpi_get_devices("IBM0068",
>> acpi_check_cb,
>>>>>>>> &found, NULL)) && found; // same as above
>>>>>>>>
>>>>>>>> 3.         if (led_set_func(TPACPI_LED_MUTE, false) >= 0) { 
>>>>>>>> //in the
>>>>>>>> sound/pci/hda/thinkpad_helper.c, hda_fixup_thinkpad_acpi()
>>>>>>> ...and this
>>>>>>>
>>>>>>>> 4. if (led_set_func(TPACPI_LED_MICMUTE, false) >= 0) { // same as
>>>>>>>> above
>>>>>>>>
>>>>>>> ...and this as well. spec->num_adc_nids is 1.
>>>>>> If we change the code like below, does the power button can work 
>>>>>> well?
>>>>>>
>>>>>> in the thinkpad_helper.c, hda_fixup_thinkpad_acpi()
>>>>>>
>>>>>>
>>>>>>           if (led_set_func(TPACPI_LED_MUTE, false) >= 0) {
>>>>>>               /*
>>>>>>               old_vmaster_hook = spec->vmaster_mute.hook;
>>>>>>               spec->vmaster_mute.hook = update_tpacpi_mute_led;
>>>>>>               removefunc = false;
>>>>>>              */
>>>>> Disabling only this block resolves the issue.
>>>> So Below two lines make the power button change to the reset button.
>>>>
>>>> drivers/platform/x86/thinkpad_acpi.c  mute_led_on_off():
>>>>
>>>> acpi_get_handle(hkey_handle, "SSMS", &temp);
>>>> acpi_evalf(hkey_handle, &output, "SSMS", "dd", 1);
>>>>
>>>>
>> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/platform/x86/thinkpad_acpi.c?id=9a417ec0c9d1f7af5394333411fc4d98adb8761b 
>>
>>
>> It seem that software mute also depend on HAUM and SAUM ACPI interface
>>
>> Seem regression of the above patch is SSMS is not supported
>>
>> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1450947
>>
>> Which models of thinkpad are tested by the author ?
> A lot, we tested this patch on all Lenovo machines with mute led we 
> have. I need to check the models name and provide them at a later time.

What I can remeber now are x230, x240, x250, L560 and x1
>
>> _______________________________________________
>> Alsa-devel mailing list
>> Alsa-devel@alsa-project.org
>> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>>
>

      reply	other threads:[~2015-07-01  9:51 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-27  6:47 [V2 PATCH] ALSA: hda - Enable mute/mic-mute LEDs for more Thinkpads with Conexant codec Hui Wang
2013-11-27  7:49 ` David Henningsson
2014-06-29 11:33 ` Jan Kiszka
2014-06-30  2:04   ` Hui Wang
2014-06-30  2:04     ` Hui Wang
2014-06-30  6:45     ` Jan Kiszka
2014-07-01  2:15       ` Hui Wang
2014-07-01  7:38         ` Jan Kiszka
2014-07-01  7:38           ` Jan Kiszka
2014-07-01  9:26           ` Hui Wang
2014-07-03  7:04             ` Jan Kiszka
2014-07-03  8:59               ` Hui Wang
2014-07-03  9:05                 ` Jan Kiszka
2014-07-03  9:05                   ` Jan Kiszka
2014-07-03  9:24                   ` Hui Wang
2014-07-03  9:24                     ` Hui Wang
2015-05-23  8:49                     ` Jan Kiszka
2015-05-23  8:49                       ` Jan Kiszka
2015-05-23 16:06                       ` Raymond Yau
2015-05-23 16:22                         ` Jan Kiszka
2015-05-23 16:22                           ` [alsa-devel] " Jan Kiszka
2015-06-24  5:37                           ` Jan Kiszka
2015-06-24  8:46                             ` Hui Wang
2015-06-25 11:02                               ` Jan Kiszka
2015-06-26  2:22                                 ` Hui Wang
2015-06-26  4:06                                   ` Jan Kiszka
2015-06-26 22:49                                   ` Henrique de Moraes Holschuh
2015-06-27  5:59                                     ` Jan Kiszka
2015-06-27 15:50                                       ` Henrique de Moraes Holschuh
2015-06-27 15:50                                         ` [alsa-devel] " Henrique de Moraes Holschuh
2015-06-29  9:06                                         ` Takashi Iwai
2015-06-29  9:06                                           ` [alsa-devel] " Takashi Iwai
2015-06-27  3:03                       ` Raymond Yau
2015-06-29  0:49                         ` Hui Wang
2015-06-29  0:49                           ` [alsa-devel] " Hui Wang
2015-07-01  9:51                           ` Hui Wang [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5593B818.2060405@canonical.com \
    --to=hui.wang@canonical.com \
    --cc=alex.hung@canonical.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=david.henningsson@canonical.com \
    --cc=jan.kiszka@web.de \
    --cc=jason77.wang@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=superquad.vortex2@gmail.com \
    --cc=tiwai@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.