Home
last modified time | relevance | path

Searched full:sequentially (Results 1 – 25 of 283) sorted by relevance

12345678910>>...12

/kernel/linux/linux-6.6/Documentation/ABI/testing/
Ddebugfs-driver-dcc36 be configured sequentially and not in a overlapping
126 be configured and enabled sequentially, e.g. list
/kernel/linux/linux-6.6/include/uapi/linux/
Dblkzoned.h27 * @BLK_ZONE_TYPE_SEQWRITE_REQ: The zone must be written sequentially
28 * @BLK_ZONE_TYPE_SEQWRITE_PREF: The zone can be written non-sequentially
/kernel/linux/linux-5.10/include/uapi/linux/
Dblkzoned.h27 * @BLK_ZONE_TYPE_SEQWRITE_REQ: The zone must be written sequentially
28 * @BLK_ZONE_TYPE_SEQWRITE_PREF: The zone can be written non-sequentially
/kernel/linux/linux-5.10/Documentation/ia64/
Dserial.rst11 /dev/ttyS1, etc., and PCI devices are named sequentially
27 Any additional ACPI or PCI devices were registered sequentially
/kernel/linux/linux-6.6/Documentation/arch/ia64/
Dserial.rst11 /dev/ttyS1, etc., and PCI devices are named sequentially
27 Any additional ACPI or PCI devices were registered sequentially
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/interrupt-controller/
Dactions,owl-sirq.yaml38 They shall be specified sequentially from output 0 to 2.
Dfsl,irqsteer.yaml26 the input interrupts. They should be specified sequentially from
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/interrupt-controller/
Dactions,owl-sirq.yaml38 They shall be specified sequentially from output 0 to 2.
Dmicrochip,sama7g5-eic.yaml35 should be specified sequentially from output 0 to output 1.
Dfsl,irqsteer.yaml26 the input interrupts. They should be specified sequentially from
/kernel/linux/linux-6.6/drivers/gpu/drm/msm/disp/dpu1/
Ddpu_hw_interrupts.h20 /* All MDP_INTFn_INTR should come sequentially */
/kernel/linux/linux-5.10/Documentation/kbuild/
DKconfig.recursion-issue-0111 # by stepping through the questions it needs to address sequentially.
/kernel/linux/linux-6.6/Documentation/kbuild/
DKconfig.recursion-issue-0111 # by stepping through the questions it needs to address sequentially.
/kernel/linux/linux-6.6/arch/mips/include/uapi/asm/
Ducontext.h11 * sigcontext. They are placed sequentially in memory at the end of struct
/kernel/linux/linux-5.10/arch/mips/include/uapi/asm/
Ducontext.h11 * sigcontext. They are placed sequentially in memory at the end of struct
/kernel/linux/linux-5.10/Documentation/userspace-api/media/rc/
Drc-tables.rst381 - Decrease channel sequentially
389 - Increase channel sequentially
/kernel/linux/linux-6.6/Documentation/userspace-api/media/rc/
Drc-tables.rst381 - Decrease channel sequentially
389 - Increase channel sequentially
/kernel/linux/linux-5.10/Documentation/core-api/
Didr.rst42 If you need to allocate IDs sequentially, you can use
/kernel/linux/linux-5.10/drivers/staging/media/atomisp/pci/
Datomisp_acc.h39 * this function may be called sequentially multiple times.
/kernel/linux/linux-6.6/drivers/hid/
Dhid-roccat-pyra.h102 * These are sent sequentially
/kernel/linux/linux-6.6/Documentation/core-api/
Didr.rst45 If you need to allocate IDs sequentially, you can use
/kernel/linux/linux-5.10/drivers/hid/
Dhid-roccat-pyra.h102 * These are sent sequentially
/kernel/linux/linux-5.10/tools/testing/selftests/net/
Dipv6_route_update_soft_lockup.sh39 # at 5000 and incrementing sequentially. Each client targets a unique iperf3
182 # sequentially. Since iperf3 instances may terminate unexpectedly, a
/kernel/linux/linux-6.6/tools/testing/selftests/net/
Dipv6_route_update_soft_lockup.sh39 # at 5000 and incrementing sequentially. Each client targets a unique iperf3
182 # sequentially. Since iperf3 instances may terminate unexpectedly, a
/kernel/linux/linux-5.10/drivers/misc/ibmasm/
Dcommand.c100 * Commands are executed sequentially. One command (sp->current_command)

12345678910>>...12