lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 16 Oct 2007 13:40:50 -0700
From:	Kristoffer Ericson <>
To:	dmitry <>
Cc:	linux-input <>,
	linux-main <>
Subject: Power button policy and mechanism

Greetings Dmitry,

Is the suggested approach on handling powerbutton (in keyboard driver) to simply push out the event and let userland handle it? 
The reason Im asking this is because as you might know Im maintainer for two mini-laptop style pda's (HP7xx & HP6xx)
and it would simplify my life alot if I didn't need to depend on userland applications to be able to suspend/resume.

For instance HP6XX receives an interrupt call whenever the powerbutton is pressed. Now I could just push out the event and let another program handle it but considering it would take a minimum amount of lines to let it simply suspend/resume I feel its a waste.

Previously the hp6xx has been allowed to do this "policy" way but that was when LinuxSH stod as a side branch to main tree. Now
when everything gets merged into mainline I need to decide how to do this.

This is mainly an embedded issue, but I feel it's quite important. It should apply to other devices also like for example Zaurus branches (those with keyboard and designated power button).

So in short:
1. Does mainline policy allow static power button events inside kernel (power button == suspend/resume)?
	Why/Why Not?
2. Seeing as my knowledge about this area isn't the best I would appreciate all opinions on the subject from the gurus.

Best wishes
Kristoffer Ericson

Kristoffer Ericson <>
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists