AnsweredAssumed Answered

input event after resume

Question asked by charles huang on Mar 20, 2017
Latest reply on Mar 27, 2017 by igorpadykov

Hi

 

Yocto 2.0/2.1

I have a question about input evet after system resume

I used evtest to monitor input event 

And "echo mem > /system/power/state" to make system sleep 

 

Test Steps as below:

1.evtest /dev/input/event0 &

2.echo mem > /sys/power/state

3.push gpio key to make system resume

 

In i.MX6 Quad core CPU

 

Disabling non-boot CPUs ...
CPU1: shutdown
CPU2: shutdown
CPU3: shutdown
Enabling non-boot CPUs ...
CPU1 is up
CPU2 is up
CPU3 is up
PM: noirq resume of devices complete after 0.596 msecs
PM: early resume of devices complete after 0.646 msecs
PM: resume of devices complete after 197.876 msecs
PM: resume devices took 0.200 seconds
Restarting tasks ... Event: time 1490021678.804272, --done.
------------ SYN_REPORT ------------
root@imx6qrom5420b1:~# ata1: SATA link down (SStatus 0 SControl 300)

--------------------------------------------------------------------------------------------------------------------------

In i.MX6 Dual or Solo core cpu (or I disabled Quad core cpu to 2 cpu core)

 

Disabling non-boot CPUs ...
PM: noirq resume of devices complete after 0.628 msecs
PM: early resume of devices complete after 0.658 msecs
PM: resume of devices complete after 199.137 msecs
PM: resume devices took 0.200 seconds
Restarting tasks ... Event: time 1490022210.526038, --done.
------------ SYN_REPORT ------------
Event: time 1490022210.622078, type 1 (EV_KEY), code 116 (KEY_POWER), value 1
Event: time 1490022210.622078, -------------- SYN_REPORT ------------
Event: time 1490022213.012175, type 1 (EV_KEY), code 116 (KEY_POWER), value 0
Event: time 1490022213.012175, -------------- SYN_REPORT ------------
root@imx6qrom5420b1:~# ata1: SATA link down (SStatus 0 SControl 300)

 

I wonder why evtest will get key event after resume in Dual/solo cpu, but Quad core won't?

 

thanks 

Outcomes