From: Pavel Machek <pavel@ucw.cz>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: Henrique de Moraes Holschuh <ibm-acpi@hmh.eng.br>,
ibm-acpi-devel@lists.sourceforge.net,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: ThinkPad T480s & LED_MUTE, LED_MICMUTE
Date: Fri, 15 Jun 2018 13:26:06 +0200 [thread overview]
Message-ID: <20180615112606.GA3986@amd> (raw)
In-Reply-To: <20180608111057.4wxpg7m7nm7suf6n@pali>
[-- Attachment #1: Type: text/plain, Size: 1340 bytes --]
Hi!
> Hi! With up-to-date thinkpad_acpi.ko driver on ThinkPad T480s I'm seeing
> a strange behavior of LEDs which are integrated into mic mute (Fn+F4)
> and mute (Fn+F1) keys.
>
> When thinkpad_acpi.ko is not loaded, then mute key is working fine. When
> pressed, it correctly generates KEY_MUTE on AT Translated Set 2 keyboard
> input device and also turn on/of mute led. But when micmute key is
> pressed then, nothing happen. No key event is reported and also led is
> not turned on/off.
>
> On the other hand, when thinkpad_acpi.ko is loaded, then both buttons
> mute and micmute correctly generates input events; mute via AT keyboard
> and micmute via ThinkPad Extra Buttons. But led is not changed. When
> thinkpad_acpi.ko is loaded it turn off both leds (mute and micmute) and
> leds after pressing any of those buttons, leds are not turned on again.
With thinkpad_acpi.ko loaded, kernel should handle the LEDs, right? Do
we have a support for that? Do they have directories in
/sys/class/leds? What are the triggers there?
With thinkpad_acpi.ko unloaded, hardware drives the LEDs, so nothing
for us to do...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-06-15 11:26 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 [this message]
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
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=20180615112606.GA3986@amd \
--to=pavel@ucw.cz \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=ibm-acpi@hmh.eng.br \
--cc=linux-kernel@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=platform-driver-x86@vger.kernel.org \
/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