[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180615123007.nxsymdvr3nj3it5i@khazad-dum.debian.net>
Date: Fri, 15 Jun 2018 09:30:07 -0300
From: Henrique de Moraes Holschuh <hmh@....eng.br>
To: Pali Rohár <pali.rohar@...il.com>
Cc: Pavel Machek <pavel@....cz>,
Henrique de Moraes Holschuh <ibm-acpi@....eng.br>,
ibm-acpi-devel@...ts.sourceforge.net,
platform-driver-x86@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: ThinkPad T480s & LED_MUTE, LED_MICMUTE
On Fri, 15 Jun 2018, Pali Rohár wrote:
> Henrique, any idea why there are no exported led classes for mute and
> micmute? And how are suppose to be controlled?
I have to look into the code, it was contributed by someone who had
access to the proper hardware to test it.
But the way *I* would like it to work is this:
1. When implemented in *hardware* or *EC*, let the hardware and EC take
full control, and never allow the operating system to mess with it.
So, it becomes much harder for that LED to "lie".
2. Otherwise implement it in-kernel, so that userspace cannot unmute
when the human has activated the "mute" switch, and the LED cannot be
controlled by userspace to lie (report mute when it is not mute).
It might, or might not be possible to achieve the above.
> > With thinkpad_acpi.ko unloaded, hardware drives the LEDs, so nothing
> > for us to do...
>
> So somehow tell thinkpad_acpi.ko to let hardware control those LEDs when
> thinkpad_acpi.ko is loaded?
I.e. look into the DSDT and XSDT, to find out what it is doing. It will
be there: it is very rare for the thinkpad EC itself to implement these
behavior changes.
--
Henrique Holschuh
Powered by blists - more mailing lists