linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhang Rui <rui.zhang@intel.com>
To: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
Cc: "linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: Input event for blocking touchpad
Date: Tue, 30 Nov 2010 09:34:13 +0800	[thread overview]
Message-ID: <1291080853.3283.282.camel@rui> (raw)
In-Reply-To: <20101126211056.GD3819@barata.holoscopio.com>

On Sat, 2010-11-27 at 05:10 +0800, Thadeu Lima de Souza Cascardo wrote:
> Hello,
> 
> I have a notebook with an ACPI system that notifies about the pressing
> of the key for blocking touchpad. However, it does not notify it by
> itself. I was considering sending the event to userspace and let it does
> the blocking.
> 
how do you know the event is sent via ACPI?

please try "cat /proc/interrupts > interrupt-1;
grep . /sys/firmware/acpi/interrupts/* > gpe-1; sleep 5;
cat /proc/interrupts > interrupt-2;
grep . /sys/firmware/acpi/interrupts/* > gpe-2", and press the block key
during the 5 seconds sleep.
Then please attach the 4 files here to see if there are ACPI interrupts
generated by the key pressing.

thanks,
rui
> Since other keys are also notified by this same ACPI object, it's even
> more natural that I use an input device to send this to userspace.
> 
> The problem is: there seems to be no event to represent this. Any
> suggestions?
> 
> Best regards,
> Cascardo.



  parent reply	other threads:[~2010-11-30  1:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-26 21:10 Input event for blocking touchpad Thadeu Lima de Souza Cascardo
2010-11-28  8:07 ` Dmitry Torokhov
2010-11-28 14:38   ` Bastien Nocera
2010-11-30  1:34 ` Zhang Rui [this message]
2010-11-30  1:56   ` Thadeu Lima de Souza Cascardo

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=1291080853.3283.282.camel@rui \
    --to=rui.zhang@intel.com \
    --cc=cascardo@holoscopio.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-input@vger.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 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).