Home
last modified time | relevance | path

Searched full:raised (Results 1 – 25 of 206) sorted by relevance

123456789

/linux/Documentation/devicetree/bindings/interrupt-controller/
H A Dvia,vt8500-intc.yaml31 Interrupt number raised by the IRQ0 output of this controller
34 Interrupt number raised by the IRQ1 output of this controller
37 Interrupt number raised by the IRQ2 output of this controller
40 Interrupt number raised by the IRQ3 output of this controller
43 Interrupt number raised by the IRQ4 output of this controller
46 Interrupt number raised by the IRQ5 output of this controller
49 Interrupt number raised by the IRQ6 output of this controller
52 Interrupt number raised by the IRQ7 output of this controller
/linux/lib/math/
H A Dint_pow.c14 * @base: base which will be raised to the given power
15 * @exp: power to be raised to
17 * Computes: pow(base, exp), i.e. @base raised to the @exp power
/linux/kernel/
H A Dirq_work.c186 struct llist_head *raised, *lazy; in irq_work_needs_cpu() local
188 raised = this_cpu_ptr(&raised_list); in irq_work_needs_cpu()
191 if (llist_empty(raised) || arch_irq_work_has_interrupt()) in irq_work_needs_cpu()
271 struct llist_head *raised = this_cpu_ptr(&raised_list); in irq_work_tick() local
273 if (!llist_empty(raised) && !arch_irq_work_has_interrupt()) in irq_work_tick()
274 irq_work_run_list(raised); in irq_work_tick()
/linux/tools/testing/selftests/x86/
H A Dtest_FCOMI.c102 " fnclex""\n" // fld of a qnan raised FE_INVALID, clear it in test_qnan()
131 " fnclex""\n" // fld of a qnan raised FE_INVALID, clear it in testu_qnan()
160 // " fnclex""\n" // flds of a snan raised FE_INVALID, clear it in testu_snan()
246 " fnclex""\n" // fld of a qnan raised FE_INVALID, clear it in testp_qnan()
274 " fnclex""\n" // fld of a qnan raised FE_INVALID, clear it in testup_qnan()
/linux/Documentation/devicetree/bindings/power/supply/
H A Ddlg,da9150-fuel-gauge.yaml27 description: Battery discharge level (%) where warning event raised.
34 Battery discharge level (%) where critical event raised.
/linux/fs/tests/
H A Dexec_kunit.c40 * 0 rlim_stack will get raised to ARG_MAX. With 1 string pointer,
45 /* Validate that argc is always raised to a minimum of 1. */
49 * 0 rlim_stack will get raised to ARG_MAX. With pointers filling ARG_MAX,
50 * we should see -E2BIG. (Note argc is always raised to at least 1.)
/linux/arch/powerpc/math-emu/
H A Dfdiv.c33 printk("%s: FPSCR_VXZDZ raised\n", __func__); in fdiv()
39 printk("%s: FPSCR_VXIDI raised\n", __func__); in fdiv()
H A Dfdivs.c34 printk("%s: FPSCR_VXZDZ raised\n", __func__); in fdivs()
40 printk("%s: FPSCR_VXIDI raised\n", __func__); in fdivs()
/linux/Documentation/driver-api/media/
H A Dv4l2-event.rst24 raised by the driver.
41 so that an event can be raised by that object. So the ``node`` field can
50 - struct v4l2_subscribed_event has a ringbuffer of raised
60 callbacks are called when a new event is raised and there is no more room.
/linux/include/linux/
H A Dhil_mlc.h136 struct semaphore csem; /* Raised when loop idle */
139 struct semaphore osem; /* Raised when outpacket dispatched */
143 struct semaphore isem; /* Raised when a packet arrives */
/linux/arch/x86/include/uapi/asm/
H A Ducontext.h40 * despite the fact that the SS selector when the signal was raised is
47 * the signal was raised.. Old kernels would lose track of the
/linux/Documentation/arch/arm64/
H A Dtagged-pointers.rst40 result in an error code being returned, a (fatal) signal being raised,
70 For signals raised in response to watchpoint debug exceptions, the
H A Dtagged-address-abi.rst102 result in an error code being returned, a (fatal) signal being raised,
133 being returned, a (fatal) signal being raised, or other modes of
/linux/Documentation/admin-guide/perf/
H A Dimx-ddr.rst13 interrupt is raised. If any other counter overflows, it continues counting, and
14 no interrupt is raised.
/linux/arch/arm/nwfpe/
H A Dsoftfloat-specialize106 exception is raised.
138 signaling NaN, the invalid exception is raised.
200 exception is raised.
235 signaling NaN, the invalid exception is raised.
308 invalid exception is raised.
344 `b' is a signaling NaN, the invalid exception is raised.
/linux/arch/x86/platform/uv/
H A Duv_irq.c179 * interrupt is raised.
205 * was raised.
/linux/Documentation/ABI/testing/
H A Dusb-uevent6 longer functional a uevent will be raised. The uevent will
/linux/Documentation/devicetree/bindings/pci/
H A Dsnps,dw-pcie-ep.yaml151 Application-specific IRQ raised depending on the vendor-specific
160 Combined interrupt signal raised when the controller has sent an
/linux/tools/testing/selftests/net/lib/py/
H A Dksft.py177 _fail(f"Expected exception {str(self.expected_type.__name__)}, none raised")
179 _fail(f"Expected exception {str(self.expected_type.__name__)}, raised {str(exc_type.__name__)}")
/linux/block/
H A Dbfq-iosched.c71 * weight-raised while it is deemed interactive, this maximum time
318 * weight-raised at the beginning of their I/O. On the opposite end,
319 * while being weight-raised, these applications
353 * have no right to be weight-raised any longer.
896 * This holds even if low_latency is on, because weight-raised queues
912 * non-weight-raised, and hence change its weight, and in bfq_weights_tree_add()
1110 * mplayer took 23 seconds to start, if constantly weight-raised. in bfq_wr_duration()
1721 * raised at startup (as for any newly in bfq_update_bfqq_wr_on_rq_arrival()
1735 * weight-raised while they are pending. in bfq_update_bfqq_wr_on_rq_arrival()
1842 * bfqq deserves to be weight-raised if: in bfq_bfqq_handle_idle_busy_switch()
[all …]
/linux/lib/math/tests/
H A Dint_pow_kunit.c20 { 5, 5, 3125, "Five raised to the fifth power" },
/linux/Documentation/devicetree/bindings/iio/proximity/
H A Dparallax-ping.yaml14 - ping-gpios is raised by the driver to start measurement
/linux/tools/testing/selftests/arm64/signal/
H A Dsignals.S44 * words we are sure no bad fatal signal has been raised till now
/linux/include/linux/irqchip/
H A Dirq-bcm2836.h42 * use mailbox 0 for IPIs. The mailbox's interrupt is raised while
/linux/Documentation/input/devices/
H A Dcs461x.rst22 behavior in my case was not raised the requirement of joystick calibration.

123456789