Home
last modified time | relevance | path

Searched refs:KEY_QUESTION (Results 1 – 10 of 10) sorted by relevance

/openbmc/u-boot/include/dt-bindings/input/
H A Dlinux-event-codes.h290 #define KEY_QUESTION 214 macro
/openbmc/qemu/include/standard-headers/linux/
H A Dinput-event-codes.h292 #define KEY_QUESTION 214 macro
/openbmc/linux/include/dt-bindings/input/
H A Dlinux-event-codes.h292 #define KEY_QUESTION 214 macro
/openbmc/linux/include/uapi/linux/
H A Dinput-event-codes.h292 #define KEY_QUESTION 214 macro
/openbmc/linux/arch/arm/mach-omap1/
H A Dboard-ams-delta.c50 KEY(0, 2, KEY_QUESTION), /* Directory */
/openbmc/linux/drivers/hid/
H A Dhid-debug.c870 [KEY_QUESTION] = "Question", [KEY_EMAIL] = "Email",
H A Dhid-input.c1303 case 0x073: map_key_clear(KEY_QUESTION); break; in hidinput_configure_usage()
/openbmc/linux/drivers/input/misc/
H A Dati_remote2.c176 { 0xbe, KEY_QUESTION },
/openbmc/u-boot/arch/arm/dts/
H A Dtegra20-harmony.dts589 MATRIX_KEY(0x1F, 0x04, KEY_QUESTION)>;
/openbmc/linux/arch/arm/boot/dts/nvidia/
H A Dtegra20-harmony.dts559 MATRIX_KEY(0x1F, 0x04, KEY_QUESTION)>;