Re: [PATCH 4/8] sonypi: rework input support

[Pavel Machek]

Hi!

> +/* Correspondance table between sonypi events and input layer events */
> +struct {
> +	int sonypiev;
> +	int inputev;
> +} sonypi_inputkeys[] = {
> +	{ SONYPI_EVENT_CAPTURE_PRESSED,	 	KEY_CAMERA },
> +	{ SONYPI_EVENT_FNKEY_ONLY, 		KEY_FN },
> +	{ SONYPI_EVENT_FNKEY_ESC, 		KEY_FN_ESC },
> +	{ SONYPI_EVENT_FNKEY_F1, 		KEY_FN_F1 },
> +	{ SONYPI_EVENT_FNKEY_F2, 		KEY_FN_F2 },
> +	{ SONYPI_EVENT_FNKEY_F3, 		KEY_FN_F3 },
> +	{ SONYPI_EVENT_FNKEY_F4, 		KEY_FN_F4 },
> +	{ SONYPI_EVENT_FNKEY_F5, 		KEY_FN_F5 },
> +	{ SONYPI_EVENT_FNKEY_F6, 		KEY_FN_F6 },
> +	{ SONYPI_EVENT_FNKEY_F7, 		KEY_FN_F7 },
> +	{ SONYPI_EVENT_FNKEY_F8, 		KEY_FN_F8 },
> +	{ SONYPI_EVENT_FNKEY_F9,		KEY_FN_F9 },
> +	{ SONYPI_EVENT_FNKEY_F10,		KEY_FN_F10 },
> +	{ SONYPI_EVENT_FNKEY_F11, 		KEY_FN_F11 },
> +	{ SONYPI_EVENT_FNKEY_F12,		KEY_FN_F12 },
> +	{ SONYPI_EVENT_FNKEY_1, 		KEY_FN_1 },
> +	{ SONYPI_EVENT_FNKEY_2, 		KEY_FN_2 },
> +	{ SONYPI_EVENT_FNKEY_D,			KEY_FN_D },
> +	{ SONYPI_EVENT_FNKEY_E,			KEY_FN_E },
> +	{ SONYPI_EVENT_FNKEY_F,			KEY_FN_F },
> +	{ SONYPI_EVENT_FNKEY_S,			KEY_FN_S },
> +	{ SONYPI_EVENT_FNKEY_B,			KEY_FN_B },
> +	{ SONYPI_EVENT_BLUETOOTH_PRESSED, 	KEY_BLUE },
> +	{ SONYPI_EVENT_BLUETOOTH_ON, 		KEY_BLUE },
> +	{ SONYPI_EVENT_PKEY_P1, 		KEY_PROG1 },
> +	{ SONYPI_EVENT_PKEY_P2, 		KEY_PROG2 },
> +	{ SONYPI_EVENT_PKEY_P3, 		KEY_PROG3 },
> +	{ SONYPI_EVENT_BACK_PRESSED, 		KEY_BACK },
> +	{ SONYPI_EVENT_HELP_PRESSED, 		KEY_HELP },
> +	{ SONYPI_EVENT_ZOOM_PRESSED, 		KEY_ZOOM },
> +	{ SONYPI_EVENT_THUMBPHRASE_PRESSED, 	BTN_THUMB },
> +	{ 0, 0 },
> +};
>  

KEY_FN_D does not sound too usefull (similar for FN_F1..FN_F12). Are
there some pictures on those keys? Mapping FN_F3 to for example
KEY_SUSPEND would be usefull...
								Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/