Skip to contentSkip to conversation

LID switch and /dev/input/event*

DISCUSSION Németh Márton 2 participants 4 messages Aug 23, 2008 – Aug 26, 2008

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

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)

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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#1 lore raw
Quoted 12 lines · Németh Márton

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:

Quoted 9 lines
# 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.

Quoted 16 lines

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:

Quoted 8 lines

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 [email protected]
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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#2 lore raw
Quoted 30 lines · Zhao Yakui
Quoted 12 lines · Németh Márton

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:

Quoted 9 lines
# 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.

Quoted 8 lines

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.

What I could find out since then is that the Linux kernel 2.6.25 is working correctly, but 2.6.26-rc3 is bad. I am about to "git bisect" the problem and I'll create a bugreport and provide the asked information. This will take some time, however, as I am currently busy with different topics.

Quoted 15 lines
Quoted 15 lines

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:

Quoted 11 lines
Quoted 8 lines

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 [email protected]
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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#3 lore raw
Quoted 38 lines · Németh Márton
Quoted 37 lines · Zhao Yakui
Quoted 12 lines · Németh Márton

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:

Quoted 9 lines
# 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

Quoted 7 lines
Quoted 1 line

Thanks.

What I could find out since then is that the Linux kernel 2.6.25 is working correctly, but 2.6.26-rc3 is bad. I am about to "git bisect" the problem and I'll create a bugreport and provide the asked information. This will take some time, however, as I am currently busy with different topics.

Bug report was created: http://bugzilla.kernel.org/show_bug.cgi?id=11428

Quoted 11 lines
Quoted 11 lines
Quoted 11 lines

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

Quoted 8 lines
Quoted 8 lines
Quoted 8 lines

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-input" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html