From: "Pali Rohár" <pali.rohar@gmail.com>
To: Damjan Georgievski <gdamjan@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>,
ibm-acpi-devel@lists.sourceforge.net,
Henrique de Moraes Holschuh <ibm-acpi@hmh.eng.br>,
linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Subject: Re: [ibm-acpi-devel] ThinkPad T480s & LED_MUTE, LED_MICMUTE
Date: Thu, 21 Jun 2018 13:40:45 +0200 [thread overview]
Message-ID: <20180621114045.tffl5duczhunuzcl@pali> (raw)
In-Reply-To: <CAEk1YH6-b3HtBN335XNxeYRWCCsBm52kC95_EZH3B4G-_TP5Pw@mail.gmail.com>
On Thursday 21 June 2018 13:35:21 Damjan Georgievski wrote:
> > I applied them to Debian's kernel (with slightly modification) and they
> > are working fine. Via "alsamixer -c 0" I can change "Mic Mute-LED Mode"
> > to "Follow Capture" and then led is ON only when microphone is ON.
> > Recording from microphone is working in both configurations.
>
> hm this is the opposite of how it works on my T450s and X1, where the
> led is ON when microphone is muted.
Purpose of this patch it to allow user to configure that LED. As I wrote
above, when I *changed* "Mic Mute-LED Mode" to "Follow Capture" in
alsamixer, then led is ON when mic is ON. Default configuration (prior
changing anything) in alsamixer is "Follow Mute" when led is ON when mic
is OFF. That patch allows you to change how LED behave.
> (I do wish the led would be ON when the microphone is not muted ie. listening)
--
Pali Rohár
pali.rohar@gmail.com
next prev parent reply other threads:[~2018-06-21 11:40 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-08 11:10 ThinkPad T480s & LED_MUTE, LED_MICMUTE Pali Rohár
2018-06-15 11:26 ` Pavel Machek
2018-06-15 11:37 ` Pali Rohár
2018-06-15 12:30 ` Henrique de Moraes Holschuh
2018-06-15 19:09 ` Pali Rohár
2018-06-15 23:36 ` Henrique de Moraes Holschuh
2018-06-16 7:33 ` Pavel Machek
2018-06-16 14:12 ` Henrique de Moraes Holschuh
2018-06-16 15:58 ` Pavel Machek
2018-06-18 10:11 ` Pali Rohár
2018-06-21 11:37 ` Pali Rohár
2018-06-15 12:51 ` Takashi Iwai
2018-06-15 19:09 ` Pali Rohár
2018-06-16 7:05 ` Takashi Iwai
2018-06-16 15:43 ` Pali Rohár
2018-06-16 16:02 ` Takashi Iwai
2018-06-18 10:28 ` Pali Rohár
2018-06-18 10:36 ` Takashi Iwai
2018-06-18 11:21 ` Pali Rohár
2018-06-18 11:26 ` Pali Rohár
2018-06-18 15:35 ` Takashi Iwai
2018-06-21 11:30 ` Pali Rohár
2018-06-21 11:35 ` [ibm-acpi-devel] " Damjan Georgievski
2018-06-21 11:39 ` Takashi Iwai
2018-06-23 12:46 ` Damjan Georgievski
2018-06-21 11:40 ` Pali Rohár [this message]
2018-06-19 8:37 ` Pali Rohár
2018-06-19 8:42 ` Takashi Iwai
2018-06-21 11:24 ` Pali Rohár
2018-06-21 11:29 ` Takashi Iwai
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=20180621114045.tffl5duczhunuzcl@pali \
--to=pali.rohar@gmail.com \
--cc=gdamjan@gmail.com \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=ibm-acpi@hmh.eng.br \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox