Difference between revisions of "HP TP Key mapping"

From WebOS Internals
Jump to navigation Jump to search
m (Undo revision 18283 by Jack87 (talk))
 
(5 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== HP TouchPad's Key Mapping for Device Buttons==
+
== HP TouchPad key mappings for device buttons ==
  
This page is under construction and is served as a reference page for now
+
=== 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
+
event0 covers multiple GPIO keys
  
KEY_REPLY looks to be the home button
+
event0 has 4 keys - KEY_VOLUMEDOWN, KEY_VOLUMEUP, KEY_REPLY and ?
  
event0 they names are self-explanitory except KEY_REPLY is the home key
+
event0 they names are self-explanatory except KEY_REPLY is the home key... the key labeled ? is literally labeled as ? and it's purpose is unknown
  
event1 is pmic8058_pwrkey   
+
event1 is pmic8058_pwrkey  with KEY_END and KEY_POWER
  
 
event2 is headset
 
event2 is headset
  
power button '''tap''' hits KEY_END over event1
 
  
'''tapping''' power sends KEY_END over event1, '''holding''' it sends KEY_POWER
+
'''tapping''' power sends KEY_END over event1, '''holding''' it (for 1/2 second) sends KEY_POWER
  
 
--event0 is on the CPU itself.
 
--event0 is on the CPU itself.
Line 103: Line 106:
 
----
 
----
  
 
+
== sysfs locations ==
 
 
== sysfs locations ==
 
  
  
 
udevadm info --query=all --name=/dev/input/event0
 
udevadm info --query=all --name=/dev/input/event0
  
/devices/platform/gpio-keys/input/input0/event0
+
<pre>
 +
P: /devices/platform/gpio-keys/input/input0/event0
  
 
E: UDEV_LOG=3
 
E: UDEV_LOG=3
Line 123: Line 125:
  
 
E: SUBSYSTEM=input
 
E: SUBSYSTEM=input
 
+
</pre>
  
 
----
 
----
Line 130: Line 132:
 
udevadm info --query=all --name=/dev/input/event1
 
udevadm info --query=all --name=/dev/input/event1
  
 +
<pre>
 
P: /devices/i2c-6/6-0055/pm8058-pwrkey/input/input1/event1
 
P: /devices/i2c-6/6-0055/pm8058-pwrkey/input/input1/event1
  
Line 143: Line 146:
  
 
E: SUBSYSTEM=input
 
E: SUBSYSTEM=input
 
+
</pre>
  
 
----
 
----
Line 150: Line 153:
 
udevadm info --query=all --name=/dev/input/event2
 
udevadm info --query=all --name=/dev/input/event2
  
 +
<pre>
 
P: /devices/platform/soc-audio.0/sound/card0/input2/event2
 
P: /devices/platform/soc-audio.0/sound/card0/input2/event2
  
Line 163: Line 167:
  
 
E: SUBSYSTEM=input
 
E: SUBSYSTEM=input
 +
</pre>

Latest revision as of 09:56, 5 September 2011

HP TouchPad key mappings for device buttons

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





event0 covers multiple GPIO keys

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

event0 they names are self-explanatory except KEY_REPLY is the home key... the key labeled ? is literally labeled as ? and it's purpose is unknown

event1 is pmic8058_pwrkey with KEY_END and KEY_POWER

event2 is headset


tapping power sends KEY_END over event1, holding it (for 1/2 second) 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 (?)




sysfs locations

udevadm info --query=all --name=/dev/input/event0

P: /devices/platform/gpio-keys/input/input0/event0

E: UDEV_LOG=3

E: DEVPATH=/devices/platform/gpio-keys/input/input0/event0

E: MAJOR=13

E: MINOR=64

E: DEVNAME=input/event0

E: SUBSYSTEM=input


udevadm info --query=all --name=/dev/input/event1

P: /devices/i2c-6/6-0055/pm8058-pwrkey/input/input1/event1

E: UDEV_LOG=3

E: DEVPATH=/devices/i2c-6/6-0055/pm8058-pwrkey/input/input1/event1

E: MAJOR=13

E: MINOR=65

E: DEVNAME=input/event1

E: SUBSYSTEM=input


udevadm info --query=all --name=/dev/input/event2

P: /devices/platform/soc-audio.0/sound/card0/input2/event2

E: UDEV_LOG=3

E: DEVPATH=/devices/platform/soc-audio.0/sound/card0/input2/event2

E: MAJOR=13

E: MINOR=66

E: DEVNAME=input/event2

E: SUBSYSTEM=input