Searched refs:demands (Results 1 – 19 of 19) sorted by relevance
/openbmc/linux/drivers/dma/ |
H A D | sun4i-dma.c | 166 struct list_head demands; member 368 if (list_empty(&contract->demands)) { in __execute_vchan_pending() 375 } while (list_empty(&contract->demands)); in __execute_vchan_pending() 378 promise = list_first_entry(&contract->demands, in __execute_vchan_pending() 573 INIT_LIST_HEAD(&contract->demands); in generate_dma_contract() 591 promise = list_first_entry_or_null(&contract->demands, in get_next_cyclic_promise() 595 &contract->demands); in get_next_cyclic_promise() 596 promise = list_first_entry(&contract->demands, in get_next_cyclic_promise() 665 list_add_tail(&promise->list, &contract->demands); in sun4i_dma_prep_dma_memcpy() 784 list_add_tail(&promise->list, &contract->demands); in sun4i_dma_prep_dma_cyclic() [all …]
|
/openbmc/linux/Documentation/power/regulator/ |
H A D | overview.rst | 49 current limit to meet operation demands.
|
/openbmc/linux/Documentation/i2c/ |
H A D | slave-interface.rst | 170 state being busy is troublesome. SMBus demands to always ACK the address phase,
|
/openbmc/linux/Documentation/networking/ |
H A D | nexthop-group-resilient.rst | 71 traffic, and use those to satisfy the new next-hop distribution demands,
|
/openbmc/linux/Documentation/gpu/amdgpu/display/ |
H A D | dcn-overview.rst | 58 setup or ignored accordingly with userspace demands. For example, if we
|
/openbmc/linux/Documentation/power/ |
H A D | opp.rst | 108 as per the demands of SoC usage environment.
|
/openbmc/linux/drivers/usb/gadget/ |
H A D | Kconfig | 298 a simple CDC subset is used, placing fewer demands on USB.
|
/openbmc/u-boot/doc/ |
H A D | README.armada-secureboot | 308 ARMADA SoC demands that whole fuse lines (64 bit values) have to be written as
|
/openbmc/linux/drivers/usb/gadget/legacy/ |
H A D | Kconfig | 133 is used, placing fewer demands on USB.
|
/openbmc/linux/Documentation/cdrom/ |
H A D | cdrom-standard.rst | 610 nothing wrong with this, but a good control of the `CD player` demands 630 secondarily for playing audio discs, have different demands for the
|
/openbmc/linux/Documentation/driver-api/usb/ |
H A D | gadget.rst | 37 I/O processing doesn't imply large demands for memory or CPU
|
/openbmc/u-boot/common/ |
H A D | dlmalloc.src | 113 Alignnment demands, plus the minimum allocatable size restriction 642 system-level demands of a long-lived program down to a bare 729 helps keep the system level memory demands of a long-lived
|
/openbmc/qemu/docs/devel/ |
H A D | multi-process.rst | 820 ordering demands that a load cannot complete before all older stores to
|
/openbmc/linux/Documentation/admin-guide/media/ |
H A D | vivid.rst | 849 demands a lot of the CPU. For large resolutions this becomes
|
/openbmc/qemu/docs/interop/ |
H A D | vhost-user.rst | 1865 The original vhost-user specification only demands replies for certain
|
/openbmc/linux/Documentation/admin-guide/ |
H A D | reporting-issues.rst | 248 demands more than other FLOSS projects. We'd love to make it simpler. But
|
/openbmc/linux/tools/memory-model/Documentation/ |
H A D | explanation.txt | 968 cache coherence demands.
|
/openbmc/openbmc/poky/documentation/ref-manual/ |
H A D | classes.rst | 2737 can ease your hard drive demands during builds.
|
/openbmc/openbmc/poky/meta/recipes-devtools/binutils/binutils/ |
H A D | 0008-Use-libtool-2.4.patch | 30155 # POSIX demands no paths to be encoded in archives. We have
|