Lines Matching full:enter

33  * Some parts (Enter Release, LED change) are still blocking polled here,
196  * Best effort cleanup of ENTER break codes on leaving KDB. Called on
197  * exiting KDB, when we know we processed an ENTER or KP ENTER scan
206 	 * ENTER was never pressed, or has already  in kdb_kbd_cleanup_state()
214 	 * Enter key. Need to absorb the break code here, lest it gets  in kdb_kbd_cleanup_state()
218 	 * + Need to handle KP ENTER, which has break code 0xe0 0x9c.  in kdb_kbd_cleanup_state()
219 	 * + Need to handle repeat ENTER and repeat KP ENTER. Repeats  in kdb_kbd_cleanup_state()
245 		 * ENTER, or a repeat make for KP ENTER. Either way,  in kdb_kbd_cleanup_state()
246 		 * since the second byte is equivalent to an ENTER,  in kdb_kbd_cleanup_state()
249 		 * If we see 0x1c, this must be a repeat ENTER or KP  in kdb_kbd_cleanup_state()
250 		 * ENTER (and we swallowed 0xe0 before). Try again.  in kdb_kbd_cleanup_state()
253 		 * mashed before or after pressing ENTER. Thus, if we  in kdb_kbd_cleanup_state()
256 		 * Note, if you held some key as ENTER was depressed,  in kdb_kbd_cleanup_state()