From: Hans de Goede <hansg@kernel.org>
To: Martino Papero <martino.papero@lcb.to.it>,
Iustin Ivan <iustinivan2002@gmail.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] Input: atkbd - skip deactivate for Lenovo IdeaPad Slim 3 14IWC11
Date: Wed, 30 Sep 2026 09:56:25 +0200 [thread overview]
Message-ID: <4f43465f-98ba-4722-8e29-03df20315369@kernel.org> (raw)
In-Reply-To: <3ccd6cc1-4b69-41dc-8f2b-3c7c1cd1626e@lcb.to.it>
Hi,
On 29-Sep-26 22:37, Martino Papero wrote:
>
> Il 19/09/26 02:09, Martino Papero ha scritto:
>>
>> Il 11/09/26 20:52, Hans de Goede ha scritto:
>>> Hi,
>>> I'm starting to wonder if we should not just make this behavior the default.
>>>
>>> IIRC the whole deactivate thing was added as a workaround for multi-byte scancodes
>>> getting split-up during suspend/resume. I wonder if we can come-up with some
>>> better fix for that ?
>>>
>>> Regards,
>>>
>>> Hans
>>
>>
>> Hi,
>>
>> I tested the same atkbd_deactivate_fixup on a Lenovo IdeaPad Slim 3 15IWC11 (83RR), which was affected by the keyboard issue previously discussed here:
>>
>> https://lore.kernel.org/all/20260628-ideapad-kbd-leds-v1-0-50b421d94927@gmail.com/ <https://lore.kernel.org/all/20260628-ideapad-kbd-leds-v1-0-50b421d94927@gmail.com/>
>>
>> Without any kernel quirk, the internal keyboard does not work. I had been using:
>>
>> |i8042.nopnp=1 i8042.dumbkbd=1|
>>
>> which makes the keyboard work, but prevents the Caps Lock LED from working.
>>
>> I built Fedora kernel 7.2.5 with the following additional DMI entry:
>>
>> {
>> /* Lenovo IdeaPad Slim 3 15IWC11 (83RR) */
>> .matches = {
>> DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
>> DMI_MATCH(DMI_PRODUCT_NAME, "83RR"),
>> },
>> .callback = atkbd_deactivate_fixup,
>> },|
>>
>> I booted this kernel without any i8042 command-line parameters.
>>
>> The internal keyboard and Caps Lock LED both work correctly. I also tested suspend/resume and a cold boot, with no issues so far.
>>
>> DMI:
>> LENOVO 83RR
>> LENOVO_MT_83RR_BU_idea_FM_IdeaPad Slim 3 15IWC11
>>
>> So it looks like the 83RR can use the same atkbd_deactivate_fixup as the 83RQ.
>>
>> I can test a revised patch if needed.
>>
>> Regards,
>> Martino
>
>
> Hi,
>
> Just following up on this.
>
> The 83RR is still working reliably with atkbd_deactivate_fixup after further use, without i8042.nopnp or i8042.dumbkbd.
>
> Would it be useful for me to submit a separate patch adding the Lenovo IdeaPad Slim 3 15IWC11 (83RR) to the atkbd_deactivate_fixup DMI table?
>
> I can prepare and test the patch on the affected hardware. Alternatively, if the generic solution discussed above is preferred, I am happy to test that as well.
Submitting a patch adding a quirk for this would be useful, I don't think
anyone is actually working on a generic solution so for now we will need
quirks to get these laptops to work.
Thanks & Regards,
Hans
prev parent reply other threads:[~2026-09-30 7:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 18:23 Iustin Ivan
2026-09-11 18:52 ` Hans de Goede
2026-09-19 0:09 ` Martino Papero
2026-09-29 20:37 ` Martino Papero
2026-09-30 7:56 ` 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=4f43465f-98ba-4722-8e29-03df20315369@kernel.org \
--to=hansg@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=iustinivan2002@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martino.papero@lcb.to.it \
--cc=stable@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
all inboxes | Powered by JetHome®