Home
last modified time | relevance | path

Searched refs:BREAK (Results 1 – 9 of 9) sorted by relevance

/linux-4.4.14/arch/frv/kernel/
Dbreak.S123 # handle BREAK instruction in kernel-mode exception epilogue
427 # we'll swap the real return address for one with a BREAK insn so that we can re-enable
438 # we also have to fudge PSR because the return BREAK is in kernel space and we want
439 # to get a BREAK fault not an access violation should the return be to userspace
/linux-4.4.14/drivers/scsi/mvsas/
Dmv_defs.h459 BREAK = (1U << 7), /* break received */ enumerator
/linux-4.4.14/Documentation/serial/
Dtty.txt185 BREAK status on the RS-232 port. If state is -1,
186 then the BREAK status should be turned on; if
187 state is 0, then BREAK should be turned off.
/linux-4.4.14/Documentation/
Dsysrq.txt53 You send a BREAK, then within 5 seconds a command key. Sending
54 BREAK twice is interpreted as a normal BREAK.
/linux-4.4.14/Documentation/frv/
Dgdbstub.txt114 kernel by sending an RS232 BREAK over the serial line to the GDB
Dfeatures.txt152 (2) Breakpoint via the FR-V "BREAK" instruction.
/linux-4.4.14/arch/cris/arch-v10/kernel/
Dentry.S117 ;; The system_call is called by a BREAK instruction, which works like
/linux-4.4.14/Documentation/input/
Datarikbd.txt170 keys. Any keys down at power-up are presumed to be stuck, and their BREAK
/linux-4.4.14/lib/
DKconfig.debug372 send a BREAK and then within 5 seconds a command keypress. The
1390 BIG FAT WARNING: ENABLING THIS OPTION MIGHT BREAK BOOTING ON