[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD8Lp45JbfQ2LVMT0LNV7j+D2GpCzWU36KHqaCvh9kKQOAXkNQ@mail.gmail.com>
Date: Fri, 19 Apr 2019 16:52:25 +0800
From: Daniel Drake <drake@...lessm.com>
To: Chris Chiu <chiu@...lessm.com>
Cc: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Corentin Chary <corentin.chary@...il.com>,
Darren Hart <dvhart@...radead.org>,
acpi4asus-user <acpi4asus-user@...ts.sourceforge.net>,
Platform Driver <platform-driver-x86@...r.kernel.org>,
Linux Kernel <linux-kernel@...r.kernel.org>,
Linux Upstreaming Team <linux@...lessm.com>
Subject: Re: [PATCH] platform/x86: asus-wmi: Add fn-lock mode switch support
On Thu, Apr 18, 2019 at 2:47 PM Chris Chiu <chiu@...lessm.com> wrote:
>
> Some of latest ASUS laptops support new fn-lock mode switching.
> This commit detect whether if the fn-lock option is enabled in
> BIOS setting, and toggle the fn-lock mode via a new WMI DEVID
> 0x00100023 when the corresponding notify code captured.
>
> The ASUS fn-lock mode switch is activated by pressing Fn+Esc.
> When on, keys F1 to F12 behave as applicable, with meanings
> defined by the application being used at the time. When off,
> F1 to F12 directly triggers hardware features, well known audio
> volume up/down, brightness up/down...etc, which were triggered
> by holding down Fn key and F-keys.
>
> Because there's no way to retrieve the fn-lock mode via existing
> WMI methods per ASUS spec, driver need to initialize and keep the
> fn-lock mode by itself.
>
> Signed-off-by: Chris Chiu <chiu@...lessm.com>
Reviewed-by: Daniel Drake <drake@...lessm.com>
Powered by blists - more mailing lists