linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhao Yakui <yakui.zhao@intel.com>
To: "Németh Márton" <nm127@freemail.hu>
Cc: linux-acpi <linux-acpi@vger.kernel.org>, linux-input@vger.kernel.org
Subject: Re: LID switch and /dev/input/event*
Date: Mon, 25 Aug 2008 09:11:47 +0800	[thread overview]
Message-ID: <1219626707.4116.6.camel@yakui_zhao.sh.intel.com> (raw)
In-Reply-To: <48B0849B.7070800@freemail.hu>

On Sat, 2008-08-23 at 23:43 +0200, Németh Márton wrote:
> Hi,
> 
> I am using Linux 2.6.27-rc4 on Clevo D410J laptop and the I can
> query the LID switch state like this:
> 
> # cat /proc/acpi/button/lid/LID/state
> state:      open
> # cat /proc/acpi/button/lid/LID/state
> state:      closed
> 
> If I check the event4, I get no events when the LID switch is pushed:
> 
> # evtest /dev/input/event4
> Input driver version is 1.0.0
> Input device ID: bus 0x19 vendor 0x0 product 0x5 version 0x0
> Input device name: "Lid Switch"
> Supported events:
>   Event type 0 (Sync)
>   Event type 5 (?)
>     Event code 0 (?)
> Testing ... (interrupt to exit)
It seems that the status of LID device is correct, but there is no LID
input event. Right?
Will you please enable the CONFIG_ACPI_DEBUG in kernel configuration and
boot the system with the option of "acpi.debug_layer=0x00090004
acpi.debug_level=0x01f"? 
After pressing the LID switch several times, please attach the output of
dmesg.

It will be great if you can attach the output of acpidump.

Of course you can open a new bug in bugzilla and attach the output of
dmesg, acpidump.

http://bugzilla.kernel.org/enter_bug.cgi?product=ACPI

Thanks.

> 
> The events are only reported if I suspend to RAM with "s2ram -f -p -s". I did
> the following steps:
> 
> 1. Execute "s2ram -f -p -s". Now the system suspends to RAM.
> 2. Push the LID switch and hold it down.
> 3. Wake the system with the POWER button.
> 4. After the system is up, release the LID switch to see the screen.
> 5. "evtest" reports the following line:
> 
> Event: time 1219526119.163805, type 5 (?), code 0 (?), value 1
> 
> 6. Execute "s2ram -f -p -s" again.
> 7. Wake the system with the POWER button.
> 8. "evtest" reports the following line:
> 
> Event: time 1219526913.208803, type 5 (?), code 0 (?), value 0
> 
> 	Márton Németh
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2008-08-25  0:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-23 21:43 LID switch and /dev/input/event* Németh Márton
2008-08-25  1:11 ` Zhao Yakui [this message]
2008-08-25  6:47   ` [regression] " Németh Márton
2008-08-26  5:29     ` Németh Márton

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=1219626707.4116.6.camel@yakui_zhao.sh.intel.com \
    --to=yakui.zhao@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=nm127@freemail.hu \
    /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).