From: ranshalit@gmail.com (Ran Shalit)
To: kernelnewbies@lists.kernelnewbies.org
Subject: disable input event device
Date: Wed, 28 Dec 2016 08:54:44 +0200 [thread overview]
Message-ID: <CAJ2oMhJa0-uWd0whJyQSX8t9mX73Gg6CBgFeRAQtDbARXDVBWA@mail.gmail.com> (raw)
In-Reply-To: <20161204103346.GA21178@kroah.com>
On Sun, Dec 4, 2016 at 12:33 PM, Greg KH <greg@kroah.com> wrote:
> On Sat, Dec 03, 2016 at 07:18:50PM +0200, Ran Shalit wrote:
>>
>>
>> On Sat, Dec 3, 2016 at 3:15 PM, Greg KH <greg@kroah.com> wrote:
>>
>> On Sat, Dec 03, 2016 at 02:43:30PM +0200, Ran Shalit wrote:
>> > Hello,
>> >
>> > Is there some way to disable input event device ?
>> > Maybe a way to disable its irq usage ?
>> >
>> > I actually rather do that from shell, not from kernel, because the kernel
>> > source is not available, and I thought that issue is also relevant in the
>> > forum.
>>
>> But the Linux kernel source is available, why not just not load the
>> driver for the device you are wanting to not be "connected"?
>>
>>
>> Hi Greg,
>>
>> I am trying to do that from android, in a device where the kernel source is not
>> available :( .....
>> By the way, I think the company (No.1 for D6 smartwatch) should supply the
>> source because kernel is GPL , Right ?
>
> Yes it is, please contact the company about this to get the source code
> for your device. If you have problems with this, please try the Linux
> Foundation's form for this type of thing at:
> https://www.linuxsources.org/content/open-compliance-directory-request-contact-information
> as it works really well.
>
>> Therefore I try to achieve it by doing some actions in shell.
>
> Disconnect the device from the driver by writing the device id to the
> "unbind" sysfs file for the driver that is controling the device.
> Examples of how to do this in detail should be on the web somewhere, I
> think I wrote a lwn.net article about this a long time ago...
>
Hi,
Just wanted to update:
the unbind method worked with some kernels, but not all.
In one device&kernel, after doing the unbind, on entering event, the
device immediately has boot itself !
Yet , luckily, I have found another method which works:
chmod 777 /dev/input/eventX
rm /dev/input/eventX
It works :) !
Thanks,
Ran
> good luck!
>
> greg k-h
prev parent reply other threads:[~2016-12-28 6:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-03 12:43 disable input event device Ran Shalit
2016-12-03 13:15 ` Greg KH
2016-12-03 17:18 ` Ran Shalit
2016-12-03 17:48 ` Daniel.
2016-12-03 17:59 ` Ran Shalit
2016-12-03 18:04 ` Ran Shalit
2016-12-03 18:58 ` Daniel.
2016-12-03 18:59 ` Daniel.
2016-12-03 19:13 ` Ran Shalit
2016-12-04 10:33 ` Greg KH
2016-12-04 10:43 ` Ran Shalit
2016-12-04 21:43 ` Ran Shalit
2016-12-28 6:54 ` Ran Shalit [this message]
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=CAJ2oMhJa0-uWd0whJyQSX8t9mX73Gg6CBgFeRAQtDbARXDVBWA@mail.gmail.com \
--to=ranshalit@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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).