![MYiR MYD-AM335X Development Manual Download Page 48](http://html.mh-extra.com/html/myir/myd-am335x/myd-am335x_development-manual_1862478048.webp)
volume_keys@0
Test MYD-AM335X
K2
and
K3
keypads as below:
# keypad_test -d /dev/input/event1
Event: Code = 115, Type = 1, Value=1 -- press K2
Event: Code = 0, Type = 0, Value=0
Event: Code = 115, Type = 1, Value=0 -- release K2
Event: Code = 0, Type = 0, Value=0
Event: Code = 114, Type = 1, Value=1 -- press K3
Event: Code = 0, Type = 0, Value=0
Event: Code = 114, Type = 1, Value=2
Event: Code = 0, Type = 0, Value=1
Event: Code = 114, Type = 1, Value=0 -- release K3
Event: Code = 0, Type = 0, Value=0
View the device nodes of MYD-AM335X-Y keypad, the following information
shows
K3
and
K4
keypads are corresponding to
/dev/input/event3
,
K5
keypad is corresponding to
/dev/input/event2
.
# ls /dev/input/
by-path event0 event1 event2 event3 mice mouse0
# cat /sys/class/input/event0/device/name
beeper
# cat /sys/class/input/event1/device/name
ti-tsc
# cat /sys/class/input/event2/device/name
tps65217_pwrbutton
# cat /sys/class/input/event3/device/name
volume_keys@0
Test MYD-AM335X-Y
K3
and
K4
keypads as below:
# keypad_test -d /dev/input/event3
Event: Code = 115, Type = 1, Value=1 -- press K3
Event: Code = 0, Type = 0, Value=0
Event: Code = 115, Type = 1, Value=0 -- release K3
Event: Code = 0, Type = 0, Value=0
Event: Code = 114, Type = 1, Value=1 -- press K4
Event: Code = 0, Type = 0, Value=0
Event: Code = 114, Type = 1, Value=0 -- release K4
Event: Code = 0, Type = 0, Value=0
48