From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Fabio Estevam <festevam@gmail.com>
Subject: Re: [PATCH v2] Input: i8042 - Add deferred probe support
Date: Sun, 28 Nov 2021 23:43:43 -0800 [thread overview]
Message-ID: <YaSEr9qctLBXFFzd@google.com> (raw)
In-Reply-To: <20211117063757.11380-1-tiwai@suse.de>
On Wed, Nov 17, 2021 at 07:37:57AM +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>
Applied, thank you.
--
Dmitry
prev parent reply other threads:[~2021-11-29 7:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 6:37 [PATCH v2] Input: i8042 - Add deferred probe support Takashi Iwai
2021-11-22 20:56 ` Samuel Čavoj
2021-11-23 7:39 ` Takashi Iwai
2021-11-29 7:43 ` Dmitry Torokhov [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=YaSEr9qctLBXFFzd@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=festevam@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.