Searched refs:KICK (Results 1 - 9 of 9) sorted by relevance

/linux-4.4.14/arch/metag/kernel/
H A Dkick.c8 * The Meta KICK interrupt mechanism is generally a useful feature, so
11 * a KICK interrupt is received the first function in the list is
12 * called. If that interrupt handler cannot handle the KICK the next
18 * handler must be able to detect whether the KICK was intended for it
20 * there are no IPI messages it must not signal that the KICK was
23 * The reason that we provide our own interface for calling KICK
25 * the KICK handlers require access to a CPU's pTBI structure. So we
90 * can't nest KICK interrupts in a KICK interrupt handler. kick_handler()
H A Dsmp.c454 * KICK interrupts are queued in hardware so we'll get for_each_cpu()
466 * chaining detects who the KICK was intended for. for_each_cpu()
470 * queued a KICK interrupt for 'msg'. for_each_cpu()
/linux-4.4.14/arch/sh/boards/mach-se/7724/
H A Dsdram.S64 mov.l KICK,r1
128 KICK: .long 0x80000000 label
/linux-4.4.14/drivers/clk/shmobile/
H A Dclk-rcar-gen2.c106 * Set KICK bit in FRQCRB to update hardware setting and wait for cpg_z_clk_set_rate()
/linux-4.4.14/arch/sh/kernel/cpu/sh4a/
H A Dclock-sh7724.c142 /* set KICK bit in FRQCRA to update hardware setting */ div4_kick()
/linux-4.4.14/sound/ppc/
H A Dsnd_ps3_reg.h704 |0 0 0 0 0|STATU|0 0 0| EVENT |0 0 0 0 0 0 0 0 0 0 0 0 0 0 0|R| KICK
/linux-4.4.14/drivers/net/wireless/rt2x00/
H A Drt61pci.h884 * TX_CNTL_CSR: KICK/Abort TX.
/linux-4.4.14/arch/metag/include/asm/
H A Dmetag_mem.h105 * INTER-THREAD KICK REGISTERS FOR SOFTWARE EVENT GENERATION
/linux-4.4.14/drivers/gpu/drm/i915/
H A Di915_irq.c2962 #define KICK 5 i915_hangcheck_elapsed() macro
3025 ring->hangcheck.score += KICK; for_each_ring()

Completed in 332 milliseconds