Use keycode as the name of gpio button entry. Therefore, we could guarantee one button only map to one keycode, no duplicated.
Signed-off-by: Jekyll Lai <[email protected]> --- mrst.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/mrst.c b/mrst.c index 8d76a4b..809f429 100644 --- a/mrst.c +++ b/mrst.c @@ -1086,8 +1086,8 @@ static struct gpio_keys_button gpio_button[] = { {KEY_CAMERA_FOCUS, -1, 1, "camera_half", EV_KEY, 0, 20}, {SW_KEYPAD_SLIDE, -1, 1, "MagSw1", EV_SW, 0, 20}, {SW_KEYPAD_SLIDE, -1, 1, "MagSw2", EV_SW, 0, 20}, - {KEY_HOMEPAGE, -1, 1, "home_btn", EV_KEY, 0, 20}, - {SW_ROTATE_LOCK, -1, 1, "rot_lock", EV_SW, 0, 20}, + {KEY_LEFTMETA, -1, 1, "KEY_LEFTMETA", EV_KEY, 0, 20}, + {SW_ROTATE_LOCK, -1, 1, "SW_ROTATE_LOCK", EV_SW, 0, 20}, }; static struct gpio_keys_platform_data mrst_gpio_keys = { -- 1.7.0.4 _______________________________________________ MeeGo-kernel mailing list [email protected] http://lists.meego.com/listinfo/meego-kernel
