From: Bastien Nocera <hadess@hadess.net>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Sebastian Reichel <sre@kernel.org>, Pavel Machek <pavel@ucw.cz>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Chuck Ebbert <cebbert.lkml@gmail.com>,
Henrik Rydberg <rydberg@euromail.se>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] input: Add disable sysfs entry for every input device
Date: Wed, 03 Jan 2018 02:47:29 +0100 [thread overview]
Message-ID: <1514944049.2523.28.camel@hadess.net> (raw)
In-Reply-To: <20180102215437.i3x2j6jvxtac4ntt@pali>
On Tue, 2018-01-02 at 22:54 +0100, Pali Rohár wrote:
> On Wednesday 04 January 2017 15:37:35 Bastien Nocera wrote:
> > I don't doubt that the use cases should be catered for, I
> > essentially
> > did that same work without kernel changes for GNOME. What I doubt
> > is
> > the fuzzy semantics, the fact that the device is kept opened but no
> > data is sent (that's not power saving), that whether users are
> > revoked
> > or should be revoked isn't clear, and that the goal is basically to
> > work around stupid input handling when at the console. When running
> > a
> > display manager, this is all avoided.
> >
> > If this were to go through, then the semantics and behaviour needs
> > to
> > be better explained, power saving actually made possible, and make
> > sure
> > that libinput can proxy that state to the users on the console. Or
> > an
> > ioctl added to the evdev device to disable them.
>
> So, do you mean to implement this "disable" action as ioctl for
> particular /dev/input/event* device (instead of sysfs entry)?
Yes, so the device can be powered down without the device node being
closed and made unavailable. I don't know whether that's something
that's already possible for all cases, but there's already
opportunistic in a lot of drivers and subsystems.
This opens up a whole new wave of potential problems, but it's a more
generally useful mechanism, I would think.
next prev parent reply other threads:[~2018-01-03 1:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-25 10:04 [RFC PATCH] input: Add disable sysfs entry for every input device Pali Rohár
2016-12-30 16:13 ` [RFC] " Nikita Yushchenko
2017-01-02 15:27 ` [RFC PATCH] " Bastien Nocera
2017-01-02 17:09 ` Pali Rohár
2017-01-03 11:21 ` Bastien Nocera
2017-01-04 7:43 ` Ivaylo Dimitrov
2017-01-04 14:37 ` Bastien Nocera
2017-01-05 12:48 ` Pali Rohár
2018-01-09 1:51 ` Peter Hutterer
2018-01-02 21:54 ` Pali Rohár
2018-01-03 1:47 ` Bastien Nocera [this message]
2018-01-03 9:31 ` Pali Rohár
2018-01-09 2:04 ` Peter Hutterer
2018-02-17 21:19 ` Pavel Machek
2018-02-18 22:50 ` Peter Hutterer
2017-01-17 11:07 ` Pavel Machek
2018-01-03 1:38 ` Bastien Nocera
2018-01-02 21:48 ` Pali Rohár
2018-01-03 1:43 ` Bastien Nocera
2017-01-02 16:44 ` David Herrmann
2017-01-02 17:31 ` Pali Rohár
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=1514944049.2523.28.camel@hadess.net \
--to=hadess@hadess.net \
--cc=cebbert.lkml@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=pali.rohar@gmail.com \
--cc=pavel@ucw.cz \
--cc=rydberg@euromail.se \
--cc=sre@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 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.