[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGdLNWESnxQLdxO8P_7q8ueeCXNNQ2LZ2jD+vg0grZkELjyyKQ@mail.gmail.com>
Date: Mon, 4 Jun 2018 09:46:06 -0600
From: Azael Avalos <coproscefalo@...il.com>
To: Hans de Goede <hdegoede@...hat.com>
Cc: Daniel Drake <drake@...lessm.com>, Chris Chiu <chiu@...lessm.com>,
Corentin Chary <corentin.chary@...il.com>,
Darren Hart <dvhart@...radead.org>,
Andy Shevchenko <andy.shevchenko@...il.com>,
Linux Kernel <linux-kernel@...r.kernel.org>,
Platform Driver <platform-driver-x86@...r.kernel.org>,
acpi4asus-user <acpi4asus-user@...ts.sourceforge.net>,
Linux Upstreaming Team <linux@...lessm.com>,
Bastien Nocera <hadess@...ess.net>,
Benjamin Berg <benjamin@...solutions.net>
Subject: Re: [PATCH 1/2] platform/x86: asus-wmi: Call new led hw_changed API
on kbd brightness change
Hi there
Let me add my two cents on the Toshiba side.
2018-06-04 8:23 GMT-06:00 Hans de Goede <hdegoede@...hat.com>:
>
> 1) drivers/platform/x86/toshiba_acpi.c
>
> I don't know how the key on Toshiba's behaves on models where
> it is hardwired / under Windows
With Toshiba we have two types of hardware implementations:
1st gen keyboards, supporting AUTO and FN-Z
AUTO - Turns on/off automatically after some (configurable) time
FN-Z - Creates "toshiba::kbd_backlight" and it's toggled by userspace
2nd gen keyborads, supporting AUTO, ON and OFF
AUTO - Ditto
ON - Always on
OFF - Always off
The second gen keyboards are completely driven by hardware,
userspace must be checking sysfs for "kbd_backlight_mode"
changes, however, the Toshiba interface emits the 0x92
ACPI event when we have a kbd mode change, but it's not
currently being transmitted to userspace via netlink.
Saludos
Azael
--
-- El mundo apesta y vosotros apestais tambien --
Powered by blists - more mailing lists