linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Louis Dalibard <louis.dalibard@gmail.com>
To: linux-input@vger.kernel.org
Cc: jikos@kernel.org, bentiss@kernel.org
Subject: [PATCH] HID: Ignore battery for ELAN touchscreens 2F2C and 4116 on ASUS Zenbook 14 OLED (2023) and ASUS Zenbook Pro 14 OLED (2023)
Date: Fri, 07 Jun 2024 11:46:51 +0200	[thread overview]
Message-ID: <12465690.O9o76ZdvQC@yuki-p> (raw)
In-Reply-To: <2747286.mvXUDI8C0e@yuki-p>

Hello!
Is the whitespace damage still an issue on the latest email?

On Tuesday, June 4, 2024 11:57:44 AM GMT+2 you wrote:
> The touchscreen reports a battery status of 0% and jumps to 1% when a
> stylus is used.
> The device ID was added and the battery ignore quirk was enabled for it.
> 
> Signed-off-by: Louis Dalibard <ontake@ontake.dev>
> ---
>   drivers/hid/hid-ids.h   | 2 ++
>   drivers/hid/hid-input.c | 4 ++++
>   2 files changed, 6 insertions(+)
> 
> diff --git a/drivers/hid/hid-ids.h b/drivers/hid/hid-ids.h
> index 61d2a21affa2..72d56ee7ce1b 100644
> --- a/drivers/hid/hid-ids.h
> +++ b/drivers/hid/hid-ids.h
> @@ -423,6 +423,8 @@
>   #define I2C_DEVICE_ID_HP_SPECTRE_X360_13_AW0020NG  0x29DF
>   #define I2C_DEVICE_ID_ASUS_TP420IA_TOUCHSCREEN 0x2BC8
>   #define I2C_DEVICE_ID_ASUS_GV301RA_TOUCHSCREEN 0x2C82
> +#define I2C_DEVICE_ID_ASUS_UX3402_TOUCHSCREEN 0x2F2C
> +#define I2C_DEVICE_ID_ASUS_UX6404_TOUCHSCREEN 0x4116
>   #define USB_DEVICE_ID_ASUS_UX550VE_TOUCHSCREEN 0x2544
>   #define USB_DEVICE_ID_ASUS_UX550_TOUCHSCREEN 0x2706
>   #define I2C_DEVICE_ID_SURFACE_GO_TOUCHSCREEN 0x261A
> diff --git a/drivers/hid/hid-input.c b/drivers/hid/hid-input.c
> index e03d300d2bac..0d21590e2d2c 100644
> --- a/drivers/hid/hid-input.c
> +++ b/drivers/hid/hid-input.c
> @@ -377,6 +377,10 @@ static const struct hid_device_id
> hid_battery_quirks[] = {
>     HID_BATTERY_QUIRK_IGNORE },
>    { HID_I2C_DEVICE(USB_VENDOR_ID_ELAN,
> I2C_DEVICE_ID_ASUS_GV301RA_TOUCHSCREEN),
>     HID_BATTERY_QUIRK_IGNORE },
> + { HID_I2C_DEVICE(USB_VENDOR_ID_ELAN,
> I2C_DEVICE_ID_ASUS_UX3402_TOUCHSCREEN), +  HID_BATTERY_QUIRK_IGNORE },
> + { HID_I2C_DEVICE(USB_VENDOR_ID_ELAN,
> I2C_DEVICE_ID_ASUS_UX6404_TOUCHSCREEN), +  HID_BATTERY_QUIRK_IGNORE },
>    { HID_USB_DEVICE(USB_VENDOR_ID_ELAN,
> USB_DEVICE_ID_ASUS_UX550_TOUCHSCREEN),
>     HID_BATTERY_QUIRK_IGNORE },
>    { HID_USB_DEVICE(USB_VENDOR_ID_ELAN,
> USB_DEVICE_ID_ASUS_UX550VE_TOUCHSCREEN),





  reply	other threads:[~2024-06-07  9:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-04  9:57 [PATCH] HID: Ignore battery for ELAN touchscreens 2F2C and 4116 on ASUS Zenbook 14 OLED (2023) and ASUS Zenbook Pro 14 OLED (2023) Louis Dalibard
2024-06-07  9:46 ` Louis Dalibard [this message]
2024-06-07 13:44   ` Jiri Kosina
  -- strict thread matches above, loose matches on Subject: below --
2024-06-04  9:38 Louis Dalibard
2024-06-04  9:35 Louis Dalibard
2024-06-04  9:21 Louis Dalibard
2024-06-04  9:23 ` Jiri Kosina
2024-06-02 15:13 Louis Dalibard
2024-06-04  8:39 ` Jiri Kosina

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=12465690.O9o76ZdvQC@yuki-p \
    --to=louis.dalibard@gmail.com \
    --cc=bentiss@kernel.org \
    --cc=jikos@kernel.org \
    --cc=linux-input@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;
as well as URLs for NNTP newsgroup(s).