X86 platform drivers
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Corentin Chary" <corentin.chary@gmail.com>,
	"Luke D Jones" <luke@ljones.dev>
Cc: Kai Heng Feng <kai.heng.feng@canonical.com>,
	James John <me@donjajo.com>,
	acpi4asus-user@lists.sourceforge.net,
	platform-driver-x86@vger.kernel.org
Subject: Re: [RFC 0/3] platform/x86: asus-wmi: Only map brightness codes when using asus-wmi backlight control
Date: Wed, 18 Oct 2023 12:02:13 +0200	[thread overview]
Message-ID: <2c177457-e9a1-bff7-e97d-23b3a2def3d5@redhat.com> (raw)
In-Reply-To: <20231017090725.38163-1-hdegoede@redhat.com>

Hi All,

On 10/17/23 11:07, Hans de Goede wrote:
> Hi All,
> 
> Here is a series to address the issue of some newer Asus laptop models
> sending 0x2a - 0x2c events for various keys which fall within
> the NOTIFY_BRNDOWN_MIN - NOTIFY_BRNDOWN_MAX range causing these to
> wrongly get translated to KEY_BRIGHTNESSDOWN events.
> 
> To fix this change the NOTIFY_BRNUP_MIN - NOTIFY_BRNUP_MAX +
> NOTIFY_BRNDOWN_MIN - NOTIFY_BRNDOWN_MAX key-mapping to only apply
> to old models which use the vendor specific asus-wmi interface for
> backlight control.
> 
> This series is marked as RFC because I still need to hear back
> from the reporter if this series actually fixes things.

Ok, so this has been tested now and since this is being hit by
multiple users (also see: https://bbs.archlinux.org/viewtopic.php?pid=2123716 )
I have decided to push this to pdx86/fixes now.

Note there is a chance that this may lead to regressions where
the brightness hotkeys stop working on some really old Asus laptop
models, in case they do report the NOTIFY_BRNUP_MIN - NOTIFY_BRNUP_MAX +
NOTIFY_BRNDOWN_MIN - NOTIFY_BRNDOWN_MAX keys even though another
method (acpi_video / GPU-native) is used to control the backlight.

This would be weird, but not entirely unsurprising.

Unfortunately the only way to find out if this is the case is to try,
so I've decided to move ahead with this series to fix the known issues
caused without it on newer models. I will deal with any regressions
on older models if / when they get reported.

Regards,

Hans



> Hans de Goede (3):
>   platform/x86: asus-wmi: Change ASUS_WMI_BRN_DOWN code from 0x20 to
>     0x2e
>   platform/x86: asus-wmi: Only map brightness codes when using asus-wmi
>     backlight control
>   platform/x86: asus-wmi: Map 0x2a code, Ignore 0x2b and 0x2c events
> 
>  drivers/platform/x86/asus-nb-wmi.c |  3 +++
>  drivers/platform/x86/asus-wmi.c    | 15 ++++-----------
>  drivers/platform/x86/asus-wmi.h    |  2 +-
>  3 files changed, 8 insertions(+), 12 deletions(-)
> 


      parent reply	other threads:[~2023-10-18 10:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-17  9:07 [RFC 0/3] platform/x86: asus-wmi: Only map brightness codes when using asus-wmi backlight control Hans de Goede
2023-10-17  9:07 ` [RFC 1/3] platform/x86: asus-wmi: Change ASUS_WMI_BRN_DOWN code from 0x20 to 0x2e Hans de Goede
2023-10-17  9:07 ` [RFC 2/3] platform/x86: asus-wmi: Only map brightness codes when using asus-wmi backlight control Hans de Goede
2023-10-17  9:07 ` [RFC 3/3] platform/x86: asus-wmi: Map 0x2a code, Ignore 0x2b and 0x2c events Hans de Goede
2023-10-18 10:02 ` Hans de Goede [this message]

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=2c177457-e9a1-bff7-e97d-23b3a2def3d5@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=acpi4asus-user@lists.sourceforge.net \
    --cc=andy@kernel.org \
    --cc=corentin.chary@gmail.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=kai.heng.feng@canonical.com \
    --cc=luke@ljones.dev \
    --cc=me@donjajo.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