From: Fabio Estevam <festevam@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>, linux-input@vger.kernel.org
Subject: Re: Delaying i8042 probe?
Date: Fri, 10 Sep 2021 08:07:17 -0300 [thread overview]
Message-ID: <CAOMZO5C-wFv0LmbHfZQUMMchJAwvxMxTs=eT6oby8O8k4QyoFQ@mail.gmail.com> (raw)
In-Reply-To: <s5ho890n1rh.wl-tiwai@suse.de>
Hi Takashi,
On Fri, Sep 10, 2021 at 7:50 AM Takashi Iwai <tiwai@suse.de> wrote:
>
> Hi,
>
> we've received a bug report about the missing keyboard on ASUS Zenbook
> 14 with AMD Ryzen:
> https://bugzilla.suse.com/show_bug.cgi?id=1190256
>
> In short, PS2 keyboard couldn't be probed at the cold boot, while it
> could be detected fine at the warm boot. The failure appears like:
>
> [ 0.512668] i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
> [ 0.512672] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
> [ 1.033609] i8042: Can't read CTR while initializing i8042
> [ 1.033632] i8042: probe of i8042 failed with error -5
>
> As openSUSE kernel builds PS2 drivers as built-in, and the probe at
> the early boot failed. Meanwhile, when we rebuilt the kernel with
> those drivers as modules, it starts working magically. So, this is
> likely a timing problem.
>
> A possibly workaround I can think of would be to allow re-probing the
> device at a later point. Do we have a good way for that, or a better
> alternative solution?
Would probe defer help here?
Something like this:
--- a/drivers/input/serio/i8042.c
+++ b/drivers/input/serio/i8042.c
@@ -1549,7 +1549,7 @@ static int __init i8042_probe(struct platform_device *dev)
error = i8042_controller_init();
if (error)
- return error;
+ return -EPROBE_DEFER;
#ifdef CONFIG_X86
next prev parent reply other threads:[~2021-09-10 11:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 10:49 Delaying i8042 probe? Takashi Iwai
2021-09-10 11:07 ` Fabio Estevam [this message]
2021-09-10 12:07 ` Takashi Iwai
2021-09-11 1:36 ` Fabio Estevam
2021-09-11 7:32 ` Takashi Iwai
2021-09-11 18:43 ` Fabio Estevam
2021-09-11 18:50 ` Fabio Estevam
2021-09-11 22:54 ` Dmitry Torokhov
2021-09-16 9:22 ` Takashi Iwai
2021-10-05 15:43 ` Takashi Iwai
2021-10-19 5:41 ` Takashi Iwai
2021-09-16 9:16 ` Takashi Iwai
2021-09-17 11:36 ` Fabio Estevam
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='CAOMZO5C-wFv0LmbHfZQUMMchJAwvxMxTs=eT6oby8O8k4QyoFQ@mail.gmail.com' \
--to=festevam@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=tiwai@suse.de \
/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).