mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans de Goede <hansg@kernel.org>
To: Martino Papero <martino.papero@lcb.to.it>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: atkbd - skip deactivate for Lenovo IdeaPad Slim 3 15IWC11
Date: Wed, 30 Sep 2026 22:36:14 +0200	[thread overview]
Message-ID: <4bb28c93-f4f2-498a-84e6-96670a336bbe@kernel.org> (raw)
In-Reply-To: <c0b597b8-e7ad-4fba-a2bb-5d252e3dfbd3@lcb.to.it>

Hi,

On 30-Sep-26 22:10, Martino Papero wrote:
> The internal keyboard on the Lenovo IdeaPad Slim 3 15IWC11 (83RR)
> does not work correctly with the default i8042 settings. Using
> i8042.nopnp=1 and i8042.dumbkbd=1 restores keyboard input, but prevents
> the Caps Lock LED from working. Using i8042.nopnp=1 alone does not fix
> the keyboard.
> 
> The laptop works correctly when atkbd_deactivate_fixup is used instead.
> Add a DMI quirk for the 83RR to enable it.
> 
> This was tested without any i8042 command-line parameters. Keyboard
> input and the Caps Lock LED work correctly, including after suspend
> and resume and after a cold boot.
> 
> Link: https://lore.kernel.org/all/4f43465f-98ba-4722-8e29-03df20315369@kernel.org/
> Signed-off-by: Martino Papero <martino.papero@lcb.to.it>

Thanks, patch looks good to me:

Reviewed-by: Hans de Goede <johannes.goede@oss.qualcomm.com>
Cc: stable@vger.kernel.org

Regards,

Hans


> ---
>  drivers/input/keyboard/atkbd.c | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/drivers/input/keyboard/atkbd.c b/drivers/input/keyboard/atkbd.c
> index 93650c982..b5ee5697a 100644
> --- a/drivers/input/keyboard/atkbd.c
> +++ b/drivers/input/keyboard/atkbd.c
> @@ -1938,6 +1938,14 @@ static const struct dmi_system_id atkbd_dmi_quirk_table[] __initconst = {
>  		},
>  		.callback = atkbd_deactivate_fixup,
>  	},
> +	{
> +		/* Lenovo IdeaPad Slim 3 15IWC11 (83RR) */
> +		.matches = {
> +			DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
> +			DMI_MATCH(DMI_PRODUCT_NAME, "83RR"),
> +		},
> +		.callback = atkbd_deactivate_fixup,
> +	},
>  	{
>  		/* Xiaomi Book Pro 14 (TM2424) */
>  		.matches = {
> 
> base-commit: 551c722f40809618230001baccf219193e22fc5a


      reply	other threads:[~2026-09-30 20:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30 20:10 Martino Papero
2026-09-30 20:36 ` 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=4bb28c93-f4f2-498a-84e6-96670a336bbe@kernel.org \
    --to=hansg@kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martino.papero@lcb.to.it \
    /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

all inboxes | Powered by JetHome®