From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Franz Sirl <Franz.Sirl-kernel@lauterbach.com>,
linux-input@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] macintosh/mac_hid.c: don't load by default
Date: Mon, 14 Nov 2022 16:16:13 -0800 [thread overview]
Message-ID: <Y3LaTeMxTa/7Rv7H@google.com> (raw)
In-Reply-To: <9255deb3-6c66-444d-940d-77e721d950e5@t-8ch.de>
On Tue, Nov 15, 2022 at 12:54:41AM +0100, Thomas Weißschuh wrote:
> Cc Franz who wrote the driver originally.
> (I hope I got the correct one)
>
> Hi Dmitry,
>
> On 2022-11-14 10:33-0800, Dmitry Torokhov wrote:
> > On Sun, Nov 13, 2022 at 04:30:22AM +0100, Thomas Weißschuh wrote:
> >> There should be no need to automatically load this driver on *all*
> >> machines with a keyboard.
> >>
> >> This driver is of very limited utility and has to be enabled by the user
> >> explicitly anyway.
> >> Furthermore its own header comment has deprecated it for 17 years.
> >
> > I think if someone does not need a driver they can either not enable it
> > or blacklist it in /etc/modprobe.d/... There is no need to break
> > module loading in the kernel.
>
> But nobody needs the driver as it is autoloaded in its current state.
> Without manual configuration after loading the driver does not provide any
> functionality.
>
> Furthermore the autoloading should load the driver for a specific
> hardware/resource that it can provide additional functionality for.
> Right now the driver loads automatically for any system that has an input
> device with a key and then just does nothing.
>
> It only wastes memory and confuses users why it is loaded.
>
> If somebody really needs this (fringe) driver it should be on them to load it
> it instead of everybody else having to disable it.
The driver is not enabled by default, so somebody has to enable it in
the first place. How did you end up with it?
>
> Furthermore the file has the following comment since the beginning of the git
> history in 2005:
>
> Copyright (C) 2000 Franz Sirl
>
> This file will soon be removed in favor of an uinput userspace tool.
OK, that is a separate topic, if there are no users we can remove the
driver. Do we know if this tool ever came into existence?
What I do not want is to break the autoload for one single driver
because somebody enabled it without intending to use and now tries to
implement a one-off.
>
> >> Fixes: 99b089c3c38a ("Input: Mac button emulation - implement as an input filter")
> >> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> >> ---
> >> drivers/macintosh/mac_hid.c | 2 --
> >> 1 file changed, 2 deletions(-)
> >>
> >> diff --git a/drivers/macintosh/mac_hid.c b/drivers/macintosh/mac_hid.c
> >> index d8c4d5664145..d01d28890db4 100644
> >> --- a/drivers/macintosh/mac_hid.c
> >> +++ b/drivers/macintosh/mac_hid.c
> >> @@ -149,8 +149,6 @@ static const struct input_device_id mac_hid_emumouse_ids[] = {
> >> { },
> >> };
> >>
> >> -MODULE_DEVICE_TABLE(input, mac_hid_emumouse_ids);
> >> -
> >> static struct input_handler mac_hid_emumouse_handler = {
> >> .filter = mac_hid_emumouse_filter,
> >> .connect = mac_hid_emumouse_connect,
> >>
> >> base-commit: fef7fd48922d11b22620e19f9c9101647bfe943d
> >> --
> >> 2.38.1
Thanks.
--
Dmitry
next prev parent reply other threads:[~2022-11-15 0:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-13 3:30 [PATCH] macintosh/mac_hid.c: don't load by default Thomas Weißschuh
2022-11-14 18:33 ` Dmitry Torokhov
2022-11-14 23:54 ` Thomas Weißschuh
2022-11-15 0:16 ` Dmitry Torokhov [this message]
2022-11-15 3:07 ` Thomas Weißschuh
2022-11-15 5:41 ` 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=Y3LaTeMxTa/7Rv7H@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=Franz.Sirl-kernel@lauterbach.com \
--cc=benh@kernel.crashing.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).