Home
last modified time | relevance | path

Searched full:raises (Results 1 – 25 of 93) sorted by relevance

1234

/linux-6.14.4/Documentation/devicetree/bindings/usb/
Dtwlxxxx-usb.txt6 interrupt number is the otg interrupt number that raises ID interrupts when
8 usb interrupt number that raises VBUS interrupts when the controller has to
26 interrupt number is the otg interrupt number that raises ID interrupts
/linux-6.14.4/tools/testing/selftests/drivers/sdsi/
Dsdsi_test.py123 with pytest.raises(OSError) as error:
130 with pytest.raises(OSError) as error:
160 with pytest.raises(OSError) as error:
179 with pytest.raises(OSError) as error:
183 with pytest.raises(OSError) as error:
/linux-6.14.4/tools/arch/x86/include/asm/
Dpvclock-abi.h19 * Protocol for the "version" fields is: hypervisor raises it (making
20 * it uneven) before it starts updating the fields and raises it again
/linux-6.14.4/arch/x86/include/asm/
Dpvclock-abi.h19 * Protocol for the "version" fields is: hypervisor raises it (making
20 * it uneven) before it starts updating the fields and raises it again
/linux-6.14.4/Documentation/devicetree/bindings/mailbox/
Damlogic,meson-gxbb-mhu.yaml16 MHU links are hardwired on a platform. A link raises interrupt for any
Dgoogle,gs101-mbox.yaml18 The controller just raises the interrupt to the firmware after the
Dhisilicon,hi6220-mailbox.txt7 raises an interrupt when messages are received.
Darm,mhu.yaml15 are hardwired on a platform. A link raises interrupt for any received data.
/linux-6.14.4/Documentation/devicetree/bindings/iommu/
Dapple,dart.yaml20 This DART IOMMU also raises interrupts in response to various
/linux-6.14.4/tools/testing/selftests/kvm/x86/
Dsvm_int_ctl_test.c35 /* This code raises interrupt INTR_IRQ_NUMBER in the L1's LAPIC, in l2_guest_code()
/linux-6.14.4/Documentation/networking/
Dplip.rst211 That raises the ACK line, triggering an interrupt in the receiving
212 machine. The receiving machine disables interrupts and raises its own ACK
/linux-6.14.4/arch/x86/kernel/fpu/
Dlegacy.h15 * Returns 0 on success or the trap number when the operation raises an
/linux-6.14.4/Documentation/scheduler/
Dsched-domains.rst35 through sched_tick(). It raises a softirq after the next regularly scheduled
/linux-6.14.4/Documentation/arch/arm64/
Dmemory-tagging-extension.rst68 - *Synchronous* - The kernel raises a ``SIGSEGV`` synchronously, with
74 - *Asynchronous* - The kernel raises a ``SIGSEGV``, in the offending
/linux-6.14.4/mm/
Dshuffle.c75 * generator bias. I.e. the expectation is that this shuffling raises the bar
/linux-6.14.4/Documentation/devicetree/bindings/firmware/
Dqcom,scm.yaml98 The wait-queue interrupt that firmware raises as part of handshake
/linux-6.14.4/tools/testing/selftests/powerpc/tm/
Dtm-signal-context-force-tm.c5 * This test raises a SIGUSR1 signal, and toggle the MSR[TS]
/linux-6.14.4/drivers/staging/media/atomisp/pci/
Dia_css_pipe_public.h264 /* @brief Controls when the Event generator raises an IRQ to the Host.
280 Controls when the Event generator in the CSS raises an IRQ to the Host.
/linux-6.14.4/Documentation/arch/x86/
Dshstk.rst19 to the normal stack copy. If the two differ, the processor raises a
/linux-6.14.4/scripts/clang-tools/
Dgen_compile_commands.py165 Raises:
/linux-6.14.4/drivers/ata/
Dsata_sx4.c44 hardware raises interrupt
48 hardware raises interrupt
54 hardware raises interrupt
58 hardware raises interrupt
/linux-6.14.4/arch/powerpc/platforms/powernv/
Dvas-fault.c50 * request buffers, raises interrupt on the CPU to handle the fault.
/linux-6.14.4/Documentation/i2c/
Dslave-testunit-backend.rst205 This test raises an interrupt via the SMBAlert pin which the host controller
/linux-6.14.4/arch/sparc/kernel/
Dsyscalls.S76 * XXX This raises the question, whether we can do the same on
/linux-6.14.4/tools/testing/selftests/drivers/net/
Dping.py90 So it raises an exception if mode is not 1(native mode).

1234