* disable input event device @ 2016-12-03 12:43 Ran Shalit 2016-12-03 13:15 ` Greg KH 0 siblings, 1 reply; 13+ messages in thread From: Ran Shalit @ 2016-12-03 12:43 UTC (permalink / raw) To: kernelnewbies 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. Thank you, Ranchu -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20161203/a06e13f7/attachment.html ^ permalink raw reply [flat|nested] 13+ messages in thread
* disable input event device 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 0 siblings, 1 reply; 13+ messages in thread From: Greg KH @ 2016-12-03 13:15 UTC (permalink / raw) To: kernelnewbies 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"? thanks, greg k-h ^ permalink raw reply [flat|nested] 13+ messages in thread
* disable input event device 2016-12-03 13:15 ` Greg KH @ 2016-12-03 17:18 ` Ran Shalit 2016-12-03 17:48 ` Daniel. 2016-12-04 10:33 ` Greg KH 0 siblings, 2 replies; 13+ messages in thread From: Ran Shalit @ 2016-12-03 17:18 UTC (permalink / raw) To: kernelnewbies 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 ? Therefore I try to achieve it by doing some actions in shell. Regards, Ran > thanks, > > greg k-h > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20161203/6d7bf2f2/attachment.html ^ permalink raw reply [flat|nested] 13+ messages in thread
* disable input event device 2016-12-03 17:18 ` Ran Shalit @ 2016-12-03 17:48 ` Daniel. 2016-12-03 17:59 ` Ran Shalit 2016-12-04 10:33 ` Greg KH 1 sibling, 1 reply; 13+ messages in thread From: Daniel. @ 2016-12-03 17:48 UTC (permalink / raw) To: kernelnewbies Is blacklisting it an option?? Regards, 2016-12-03 15:18 GMT-02:00 Ran Shalit <ranshalit@gmail.com>: > > > 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 ? > > Therefore I try to achieve it by doing some actions in shell. > > Regards, > Ran > >> >> thanks, >> >> greg k-h > > > > _______________________________________________ > Kernelnewbies mailing list > Kernelnewbies at kernelnewbies.org > https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies > -- "Do or do not. There is no try" Yoda Master ^ permalink raw reply [flat|nested] 13+ messages in thread
* disable input event device 2016-12-03 17:48 ` Daniel. @ 2016-12-03 17:59 ` Ran Shalit 2016-12-03 18:04 ` Ran Shalit 0 siblings, 1 reply; 13+ messages in thread From: Ran Shalit @ 2016-12-03 17:59 UTC (permalink / raw) To: kernelnewbies On Sat, Dec 3, 2016 at 7:48 PM, Daniel. <danielhilst@gmail.com> wrote: > Is blacklisting it an option?? > > I think not, because blacklist is only for loaded modules, Right ? While in android Linux, seems that all modules are built inside kernel image... > Regards, > > 2016-12-03 15:18 GMT-02:00 Ran Shalit <ranshalit@gmail.com>: > > > > > > 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 ? > > > > Therefore I try to achieve it by doing some actions in shell. > > > > Regards, > > Ran > > > >> > >> thanks, > >> > >> greg k-h > > > > > > > > _______________________________________________ > > Kernelnewbies mailing list > > Kernelnewbies at kernelnewbies.org > > https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies > > > > > > -- > "Do or do not. There is no try" > Yoda Master > > _______________________________________________ > Kernelnewbies mailing list > Kernelnewbies at kernelnewbies.org > https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20161203/8011ab2b/attachment.html ^ permalink raw reply [flat|nested] 13+ messages in thread
* disable input event device 2016-12-03 17:59 ` Ran Shalit @ 2016-12-03 18:04 ` Ran Shalit 2016-12-03 18:58 ` Daniel. 0 siblings, 1 reply; 13+ messages in thread From: Ran Shalit @ 2016-12-03 18:04 UTC (permalink / raw) To: kernelnewbies On Sat, Dec 3, 2016 at 7:59 PM, Ran Shalit <ranshalit@gmail.com> wrote: > > > On Sat, Dec 3, 2016 at 7:48 PM, Daniel. <danielhilst@gmail.com> wrote: > >> Is blacklisting it an option?? >> >> > I think not, because blacklist is only for loaded modules, Right ? > While in android Linux, seems that all modules are built inside kernel > image... > > Some more information about the touch device : I have sysfs entires for the touch device in kernel as following: /sys/devices/virtual/input/input2/event2/ root at mako:/sys/devices/virtual/input/input2 # ls capabilities event2 id modalias name phys power properties subsystem uevent uniq root at mako:/sys/devices/virtual/input/input2/event2/device # ls capabilities event2 id modalias name phys power properties subsystem uevent uniq root at mako:/sys/devices/virtual/input/input2/event2/device # cat name touch_dev Thanks, Ran > > > >> Regards, >> >> 2016-12-03 15:18 GMT-02:00 Ran Shalit <ranshalit@gmail.com>: >> > >> > >> > 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 ? >> > >> > Therefore I try to achieve it by doing some actions in shell. >> > >> > Regards, >> > Ran >> > >> >> >> >> thanks, >> >> >> >> greg k-h >> > >> > >> > >> > _______________________________________________ >> > Kernelnewbies mailing list >> > Kernelnewbies at kernelnewbies.org >> > https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies >> > >> >> >> >> -- >> "Do or do not. There is no try" >> Yoda Master >> >> _______________________________________________ >> Kernelnewbies mailing list >> Kernelnewbies at kernelnewbies.org >> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20161203/a90724fc/attachment.html ^ permalink raw reply [flat|nested] 13+ messages in thread
* disable input event device 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 0 siblings, 2 replies; 13+ messages in thread From: Daniel. @ 2016-12-03 18:58 UTC (permalink / raw) To: kernelnewbies Is xinput avaible? I know that it can be use to disable input devices, but IFAIK android use custom GUI, that is not X... 2016-12-03 16:04 GMT-02:00 Ran Shalit <ranshalit@gmail.com>: > > > On Sat, Dec 3, 2016 at 7:59 PM, Ran Shalit <ranshalit@gmail.com> wrote: >> >> >> >> On Sat, Dec 3, 2016 at 7:48 PM, Daniel. <danielhilst@gmail.com> wrote: >>> >>> Is blacklisting it an option?? >>> >> >> I think not, because blacklist is only for loaded modules, Right ? >> While in android Linux, seems that all modules are built inside kernel >> image... >> > > Some more information about the touch device : > > I have sysfs entires for the touch device in kernel as following: > > /sys/devices/virtual/input/input2/event2/ > > root at mako:/sys/devices/virtual/input/input2 # ls > capabilities > event2 > id > modalias > name > phys > power > properties > subsystem > uevent > uniq > > root at mako:/sys/devices/virtual/input/input2/event2/device # ls > capabilities > event2 > id > modalias > name > phys > power > properties > subsystem > uevent > uniq > > root at mako:/sys/devices/virtual/input/input2/event2/device # cat name > touch_dev > > > Thanks, > Ran > >> >> >> >>> >>> Regards, >>> >>> 2016-12-03 15:18 GMT-02:00 Ran Shalit <ranshalit@gmail.com>: >>> > >>> > >>> > 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 ? >>> > >>> > Therefore I try to achieve it by doing some actions in shell. >>> > >>> > Regards, >>> > Ran >>> > >>> >> >>> >> thanks, >>> >> >>> >> greg k-h >>> > >>> > >>> > >>> > _______________________________________________ >>> > Kernelnewbies mailing list >>> > Kernelnewbies at kernelnewbies.org >>> > https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies >>> > >>> >>> >>> >>> -- >>> "Do or do not. There is no try" >>> Yoda Master >>> >>> _______________________________________________ >>> Kernelnewbies mailing list >>> Kernelnewbies at kernelnewbies.org >>> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies >> >> > -- "Do or do not. There is no try" Yoda Master ^ permalink raw reply [flat|nested] 13+ messages in thread
* disable input event device 2016-12-03 18:58 ` Daniel. @ 2016-12-03 18:59 ` Daniel. 2016-12-03 19:13 ` Ran Shalit 1 sibling, 0 replies; 13+ messages in thread From: Daniel. @ 2016-12-03 18:59 UTC (permalink / raw) To: kernelnewbies it can be used* 2016-12-03 16:58 GMT-02:00 Daniel. <danielhilst@gmail.com>: > Is xinput avaible? I know that it can be use to disable input devices, > but IFAIK android use custom GUI, that is not X... > > > 2016-12-03 16:04 GMT-02:00 Ran Shalit <ranshalit@gmail.com>: >> >> >> On Sat, Dec 3, 2016 at 7:59 PM, Ran Shalit <ranshalit@gmail.com> wrote: >>> >>> >>> >>> On Sat, Dec 3, 2016 at 7:48 PM, Daniel. <danielhilst@gmail.com> wrote: >>>> >>>> Is blacklisting it an option?? >>>> >>> >>> I think not, because blacklist is only for loaded modules, Right ? >>> While in android Linux, seems that all modules are built inside kernel >>> image... >>> >> >> Some more information about the touch device : >> >> I have sysfs entires for the touch device in kernel as following: >> >> /sys/devices/virtual/input/input2/event2/ >> >> root at mako:/sys/devices/virtual/input/input2 # ls >> capabilities >> event2 >> id >> modalias >> name >> phys >> power >> properties >> subsystem >> uevent >> uniq >> >> root at mako:/sys/devices/virtual/input/input2/event2/device # ls >> capabilities >> event2 >> id >> modalias >> name >> phys >> power >> properties >> subsystem >> uevent >> uniq >> >> root at mako:/sys/devices/virtual/input/input2/event2/device # cat name >> touch_dev >> >> >> Thanks, >> Ran >> >>> >>> >>> >>>> >>>> Regards, >>>> >>>> 2016-12-03 15:18 GMT-02:00 Ran Shalit <ranshalit@gmail.com>: >>>> > >>>> > >>>> > 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 ? >>>> > >>>> > Therefore I try to achieve it by doing some actions in shell. >>>> > >>>> > Regards, >>>> > Ran >>>> > >>>> >> >>>> >> thanks, >>>> >> >>>> >> greg k-h >>>> > >>>> > >>>> > >>>> > _______________________________________________ >>>> > Kernelnewbies mailing list >>>> > Kernelnewbies at kernelnewbies.org >>>> > https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies >>>> > >>>> >>>> >>>> >>>> -- >>>> "Do or do not. There is no try" >>>> Yoda Master >>>> >>>> _______________________________________________ >>>> Kernelnewbies mailing list >>>> Kernelnewbies at kernelnewbies.org >>>> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies >>> >>> >> > > > > -- > "Do or do not. There is no try" > Yoda Master -- "Do or do not. There is no try" Yoda Master ^ permalink raw reply [flat|nested] 13+ messages in thread
* disable input event device 2016-12-03 18:58 ` Daniel. 2016-12-03 18:59 ` Daniel. @ 2016-12-03 19:13 ` Ran Shalit 1 sibling, 0 replies; 13+ messages in thread From: Ran Shalit @ 2016-12-03 19:13 UTC (permalink / raw) To: kernelnewbies On Sat, Dec 3, 2016 at 8:58 PM, Daniel. <danielhilst@gmail.com> wrote: > Is xinput avaible? I know that it can be use to disable input devices, > but IFAIK android use custom GUI, that is not X... > > > No, it's not available in Android. > 2016-12-03 16:04 GMT-02:00 Ran Shalit <ranshalit@gmail.com>: > > > > > > On Sat, Dec 3, 2016 at 7:59 PM, Ran Shalit <ranshalit@gmail.com> wrote: > >> > >> > >> > >> On Sat, Dec 3, 2016 at 7:48 PM, Daniel. <danielhilst@gmail.com> wrote: > >>> > >>> Is blacklisting it an option?? > >>> > >> > >> I think not, because blacklist is only for loaded modules, Right ? > >> While in android Linux, seems that all modules are built inside kernel > >> image... > >> > > > > Some more information about the touch device : > > > > I have sysfs entires for the touch device in kernel as following: > > > > /sys/devices/virtual/input/input2/event2/ > > > > root at mako:/sys/devices/virtual/input/input2 # ls > > capabilities > > event2 > > id > > modalias > > name > > phys > > power > > properties > > subsystem > > uevent > > uniq > > > > root at mako:/sys/devices/virtual/input/input2/event2/device # ls > > capabilities > > event2 > > id > > modalias > > name > > phys > > power > > properties > > subsystem > > uevent > > uniq > > > > root at mako:/sys/devices/virtual/input/input2/event2/device # cat name > > touch_dev > > > > > > Thanks, > > Ran > > > >> > >> > >> > >>> > >>> Regards, > >>> > >>> 2016-12-03 15:18 GMT-02:00 Ran Shalit <ranshalit@gmail.com>: > >>> > > >>> > > >>> > 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 ? > >>> > > >>> > Therefore I try to achieve it by doing some actions in shell. > >>> > > >>> > Regards, > >>> > Ran > >>> > > >>> >> > >>> >> thanks, > >>> >> > >>> >> greg k-h > >>> > > >>> > > >>> > > >>> > _______________________________________________ > >>> > Kernelnewbies mailing list > >>> > Kernelnewbies at kernelnewbies.org > >>> > https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies > >>> > > >>> > >>> > >>> > >>> -- > >>> "Do or do not. There is no try" > >>> Yoda Master > >>> > >>> _______________________________________________ > >>> Kernelnewbies mailing list > >>> Kernelnewbies at kernelnewbies.org > >>> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies > >> > >> > > > > > > -- > "Do or do not. There is no try" > Yoda Master > > _______________________________________________ > Kernelnewbies mailing list > Kernelnewbies at kernelnewbies.org > https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20161203/dfdf0993/attachment-0001.html ^ permalink raw reply [flat|nested] 13+ messages in thread
* disable input event device 2016-12-03 17:18 ` Ran Shalit 2016-12-03 17:48 ` Daniel. @ 2016-12-04 10:33 ` Greg KH 2016-12-04 10:43 ` Ran Shalit 2016-12-28 6:54 ` Ran Shalit 1 sibling, 2 replies; 13+ messages in thread From: Greg KH @ 2016-12-04 10:33 UTC (permalink / raw) To: kernelnewbies 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... good luck! greg k-h ^ permalink raw reply [flat|nested] 13+ messages in thread
* disable input event device 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 1 sibling, 1 reply; 13+ messages in thread From: Ran Shalit @ 2016-12-04 10:43 UTC (permalink / raw) To: kernelnewbies 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, Thanks for the good suggestions. I'll try both. I found your article here: https://lwn.net/Articles/143397/ Regards, Ran > good luck! > > greg k-h > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20161204/0b977e19/attachment.html ^ permalink raw reply [flat|nested] 13+ messages in thread
* disable input event device 2016-12-04 10:43 ` Ran Shalit @ 2016-12-04 21:43 ` Ran Shalit 0 siblings, 0 replies; 13+ messages in thread From: Ran Shalit @ 2016-12-04 21:43 UTC (permalink / raw) To: kernelnewbies On Sun, Dec 4, 2016 at 12:43 PM, Ran Shalit <ranshalit@gmail.com> wrote: > > > 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-directo >> ry-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, > > Thanks for the good suggestions. I'll try both. > > I found your article here: > https://lwn.net/Articles/143397/ > > Regards, > Ran > > >> good luck! >> >> greg k-h >> > > Hi, Just wanted to update the the unbind method (for disabling device such as touch screen) works perfectly with linux in general, and in android Linux too ! Many Thanks, Ran -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20161204/199a281e/attachment.html ^ permalink raw reply [flat|nested] 13+ messages in thread
* disable input event device 2016-12-04 10:33 ` Greg KH 2016-12-04 10:43 ` Ran Shalit @ 2016-12-28 6:54 ` Ran Shalit 1 sibling, 0 replies; 13+ messages in thread From: Ran Shalit @ 2016-12-28 6:54 UTC (permalink / raw) To: kernelnewbies 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 ^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2016-12-28 6:54 UTC | newest] Thread overview: 13+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 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 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).