From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-input@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Vojtech Pavlik <vojtech@suse.cz>,
Hans de Goede <hdegoede@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: i8042 - disable active multiplexing by default
Date: Fri, 10 Oct 2014 14:02:31 -0700 [thread overview]
Message-ID: <20141010210231.GA38320@dtor-ws> (raw)
In-Reply-To: <alpine.LNX.2.00.1410102252480.31343@pobox.suse.cz>
On Fri, Oct 10, 2014 at 10:59:19PM +0200, Jiri Kosina wrote:
> On Fri, 10 Oct 2014, Dmitry Torokhov wrote:
>
> > Active multiplexing is a nice feature as it allows several pointing devices
> > (such as touchpad and external mouse) use their native protocols at the
> > same time. Unfortunately many manufacturers do not implement the feature
> > properly even though they advertise it. The problematic implementations are
> > never fixed, since Windows by default does not use this mode, and move from
> > one BIOS/model of laptop to another. When active multiplexing is broken
> > turning it on usually results in touchpad, keyboard, or both unresponsive.
> >
> > With PS/2 usage on decline (most of PS/2 devices in use nowadays are
> > internal laptop touchpads), I expect number of users who have laptops with
> > working MUX implementation, docking stations with external PS/2 ports, and
> > who are still using external PS/2 mice, to be rather small. Let's flip the
> > default to be OFF and allow activating it through i8042.nomux=0 kernel
> > option. We'll also keep DMI table where we can record known good models.
>
> Being responsible for introducing a non-trivial portion of
> i8042_dmi_nomux_table[] entries:
>
> Acked-by: Jiri Kosina <jkosina@suse.cz>
>
> If nothing else, it'd make my life easier :)
>
> [ ... snip ... ]
> > diff --git a/drivers/input/serio/i8042.c b/drivers/input/serio/i8042.c
> > index f5a98af..9a97c2b 100644
> > --- a/drivers/input/serio/i8042.c
> > +++ b/drivers/input/serio/i8042.c
> > @@ -39,7 +39,7 @@ static bool i8042_noaux;
> > module_param_named(noaux, i8042_noaux, bool, 0);
> > MODULE_PARM_DESC(noaux, "Do not probe or use AUX (mouse) port.");
> >
> > -static bool i8042_nomux;
> > +static bool i8042_nomux = true;
>
> Hmmm ... perhaps if we want to be really friendly, we should warn (and I
> definitely don't mean WARN(), but rather pr_info() or something) if we
> encounter that the cmdline contains 'i8042.nomux=1'.
Warn about what? That they do not need this option anymore? They might
if they downgrade the kernel. I would not bother...
Thanks.
--
Dmitry
next prev parent reply other threads:[~2014-10-10 21:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 20:51 [PATCH] Input: i8042 - disable active multiplexing by default Dmitry Torokhov
2014-10-10 20:59 ` Jiri Kosina
2014-10-10 21:02 ` Dmitry Torokhov [this message]
2014-10-10 21:18 ` Dave Jones
2014-10-10 21:22 ` Dmitry Torokhov
2014-10-11 9:12 ` Hans de Goede
2014-10-12 14:30 ` Pavel Machek
2014-10-13 16: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=20141010210231.GA38320@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=hdegoede@redhat.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vojtech@suse.cz \
/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).