Difference between revisions of "HP TP Key mapping"

Revision as of 08:34, 27 August 2011

This page is under construction and is served as a reference page for now

event0 is the volume

event0 has 4 keys - KEY_VOLUMEDOWN, KEY_VOLUMEUP, KEY_REPLY and ?

event0 is multiple gpio keys

KEY_REPLY looks to be the home button

event0 they names are self-explanitory except KEY_REPLY is the home key

event1 is pmic8058_pwrkey

event2 is headset

power button tap hits KEY_END over event1

tapping power sends KEY_END over event1, holding it sends KEY_POWER

--event0 is on the CPU itself.

--event2 could be from the Audio Processor

evtest /dev/input/event0

Input driver version is 1.0.0

Input device ID: bus 0x19 vendor 0x1 product 0x1 version 0x100

Input device name: "gpio-keys"

Supported events:

Event type 0 (Sync)

Event type 1 (Key)

Event code 114 (VolumeDown)
Event code 115 (VolumeUp)
Event code 232 (Reply)
Event code 249 (?)

event type 5 (?)

evtest /dev/input/event1

Input driver version is 1.0.0

Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0

Input device name: "pmic8058_pwrkey"

Supported events:

Event type 0 (Sync)

Event type 1 (Key)

Event code 107 (End)
Event code 116 (Power)

evtest /dev/input/event2

Input driver version is 1.0.0

Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0

Input device name: "headset"

Supported events:

Event type 0 (Sync) Event type 1 (Key)

Event code 164 (PlayPause)

Event type 5 (?) Event code 2 (?) Event code 4 (?)

@@ Line 20: / Line 20: @@
 '''tapping''' power sends KEY_END over event1, '''holding''' it sends KEY_POWER
+--event0 is on the CPU itself.
+--event2 could be from the Audio Processor
 ----