Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751048AbeABVyo (ORCPT + 1 other); Tue, 2 Jan 2018 16:54:44 -0500 Received: from mail-wm0-f67.google.com ([74.125.82.67]:38518 "EHLO mail-wm0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750745AbeABVyk (ORCPT ); Tue, 2 Jan 2018 16:54:40 -0500 X-Google-Smtp-Source: ACJfBovdPt6sbiU6cYrCvFLco/DTjpZ/Ytv2xkTbov0ASXW7026MOk85P7uSy/wJWQNAn4iSXs5u4Q== Date: Tue, 2 Jan 2018 22:54:37 +0100 From: Pali =?utf-8?B?Um9ow6Fy?= To: Bastien Nocera Cc: Ivaylo Dimitrov , Dmitry Torokhov , Sebastian Reichel , Pavel Machek , Mauro Carvalho Chehab , Chuck Ebbert , Henrik Rydberg , linux-input@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [RFC PATCH] input: Add disable sysfs entry for every input device Message-ID: <20180102215437.i3x2j6jvxtac4ntt@pali> References: <1482660296-8432-1-git-send-email-pali.rohar@gmail.com> <1483370825.2420.8.camel@hadess.net> <201701021809.58943@pali> <1483442481.2420.12.camel@hadess.net> <60c21c4d-bb81-342a-45e1-7e92313e05d7@gmail.com> <1483540655.2420.18.camel@hadess.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1483540655.2420.18.camel@hadess.net> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: 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)? -- Pali Rohár pali.rohar@gmail.com