From: Rahul Rameshbabu <rrameshbabu@nvidia.com>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: <dmitry.torokhov@gmail.com>, <linux-input@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] Input: i8042: Add a quirk for Framework 16" laptop
Date: Wed, 06 Dec 2023 13:54:25 -0800 [thread overview]
Message-ID: <87msungfou.fsf@nvidia.com> (raw)
In-Reply-To: <20231206212140.7458-2-mario.limonciello@amd.com> (Mario Limonciello's message of "Wed, 6 Dec 2023 15:21:40 -0600")
On Wed, 06 Dec, 2023 15:21:40 -0600 Mario Limonciello <mario.limonciello@amd.com> wrote:
> The Framework 16" laptop doesn't have a PS/2 keyboard. At bootup the
> following messages are emitted:
>
> i8042: PNP: No PS/2 controller found.
> i8042: PNP: Probing ports directly.
> i8042: Can't read CTR while initializing i8042
> i8042: probe of i8042 failed with error -5
>
> There are no PNP devices as those listed in `pnp_kbd_devids` but
> i8042_pnp_init() ignores this and still runs and will continue to
> try to probe.
>
> As there is no PS/2 keyboard or mouse in this laptop, set a quirk
> to avoid this behavior.
>
> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
> ---
Reviewed-by: Rahul Rameshbabu <rrameshbabu@nvidia.com>
next prev parent reply other threads:[~2023-12-06 21:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 21:21 [PATCH v2 1/2] Input: i8042: Avoid probing if no keyboard and mouse are set in quirks Mario Limonciello
2023-12-06 21:21 ` [PATCH v2 2/2] Input: i8042: Add a quirk for Framework 16" laptop Mario Limonciello
2023-12-06 21:54 ` Rahul Rameshbabu [this message]
2023-12-08 17:57 ` Dmitry Torokhov
2023-12-08 18:08 ` Rahul Rameshbabu
2023-12-08 18:22 ` Mario Limonciello
2023-12-06 21:55 ` [PATCH v2 1/2] Input: i8042: Avoid probing if no keyboard and mouse are set in quirks Rahul Rameshbabu
2023-12-07 20:39 ` Mario Limonciello
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=87msungfou.fsf@nvidia.com \
--to=rrameshbabu@nvidia.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
/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).