From: Takashi Iwai <tiwai@suse.de>
To: "Samuel Čavoj" <samuel@cavoj.net>
Cc: Takashi Iwai <tiwai@suse.de>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
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: Tue, 23 Nov 2021 08:39:01 +0100 [thread overview]
Message-ID: <s5ho86bb9t6.wl-tiwai@suse.de> (raw)
In-Reply-To: <0ffa3c3050c5a27688168702806193f4@cavoj.net>
On Mon, 22 Nov 2021 21:56:52 +0100,
Samuel Čavoj wrote:
>
> Hi Takashi,
>
> On 2021-11-17 07:37, Takashi Iwai wrote:
> > [...]
> > 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.
>
> I own the ASUS ZenBook UX325UA and it has the exact same problem.
> Would you add it to the quirk table, or should I just submit another
> patch based on this one?
If another rewrite is requested, I can add yours in v3 patch.
Other than that, please submit the additional patch.
> The output of `dmidecode` is as follows:
>
> Handle 0x0001, DMI type 1, 27 bytes
> System Information
> Manufacturer: ASUSTeK COMPUTER INC.
> Product Name: ZenBook UX325UA_UM325UA
>
> Thank you for tracking down this problem.
>
> >
> > 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>
>
> Tested-by: Samuel Čavoj <samuel@cavoj.net>
Glad to see that the patch helps.
thanks,
Takashi
next prev parent reply other threads:[~2021-11-23 7:39 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 [this message]
2021-11-29 7:43 ` Dmitry Torokhov
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=s5ho86bb9t6.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 \
--cc=samuel@cavoj.net \
/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