From: Takashi Iwai <tiwai@suse.de>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Fabio Estevam <festevam@gmail.com>
Subject: Re: [PATCH] Input: i8042 - Add deferred probe support
Date: Wed, 17 Nov 2021 07:36:57 +0100 [thread overview]
Message-ID: <s5hr1bfnv92.wl-tiwai@suse.de> (raw)
In-Reply-To: <20211112180022.10850-1-tiwai@suse.de>
On Fri, 12 Nov 2021 19:00:22 +0100,
Takashi Iwai wrote:
>
> We've got a bug report about the non-working keyboard on ASUS ZenBook
> UX425UA. It seems that the PS/2 device isn't ready immediately at
> boot but takes some seconds to get ready. Until now, the only
> workaround is to defer the probe, but it's available only when the
> driver is a module. However, many distros, including openSUSE as in
> the original report, build the PS/2 input drivers into kernel, hence
> it won't work easily.
>
> This patch adds the support for the deferred probe for i8042 stuff as
> a workaround of the problem above. When the deferred probe mode is
> enabled and the device couldn't be probed, it'll be repeated with the
> standard deferred probe mechanism.
>
> The deferred probe mode is enabled either via the new option
> i8042.probe_defer or via the quirk table entry. As of this patch, the
> quirk table contains only ASUS ZenBook UX425UA.
>
> The deferred probe part is based on Fabio's initial work.
>
> BugLink: https://bugzilla.suse.com/show_bug.cgi?id=1190256
> Link: https://lore.kernel.org/r/s5ho890n1rh.wl-tiwai@suse.de
> Cc: Fabio Estevam <festevam@gmail.com>
> Signed-off-by: Takashi Iwai <tiwai@suse.de>
There was a typo in MODULE_PARAM_DESC(). Will resubmit v2 patch.
Takashi
prev parent reply other threads:[~2021-11-17 6:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 18:00 [PATCH] Input: i8042 - Add deferred probe support Takashi Iwai
2021-11-17 6:36 ` Takashi Iwai [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=s5hr1bfnv92.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=dmitry.torokhov@gmail.com \
--cc=festevam@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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