[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHp75VcPuhRJ8q4x7UUrJV5AMEGV2iMm6_KrVaH8+GtE3AjaOQ@mail.gmail.com>
Date: Mon, 13 Jan 2020 11:47:12 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Daniel Drake <drake@...lessm.com>
Cc: Jian-Hong Pan <jian-hong@...lessm.com>,
Corentin Chary <corentin.chary@...il.com>,
Darren Hart <dvhart@...radead.org>,
Andy Shevchenko <andy@...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>,
nweibley@...il.com
Subject: Re: [PATCH] platform/x86: asus-wmi: Fix keyboard brightness cannot be
set to 0
On Mon, Jan 13, 2020 at 5:47 AM Daniel Drake <drake@...lessm.com> wrote:
>
> On Tue, Dec 31, 2019 at 2:53 PM Daniel Drake <drake@...lessm.com> wrote:
> > Here, writing 0x80 to turn off the keyboard LED will result in an
> > additional WRAM(0x9f0, 0) call that was not there before. I think we
> > should double check this detail.
> >
> > Let's see if we can borrow one of the affected models and double check
> > this patch there before proceeding. I'll follow up internally.
>
> Asus were unable to find a product sample with the affected behaviour.
> They did provide us with one from the list I had made, but with a
> newer BIOS version where that behaviour has been eliminated. They also
> advised that always setting bit 7 is the way they do it on Windows. So
> I don't think we have the opportunity for extra verification, but it
> should be safe.
>
> Reviewed-by: Daniel Drake <drake@...lessm.com>
Thank you, Daniel! I'll queue it soon to my tree.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists