Searched refs:demands (Results 1 – 13 of 13) sorted by relevance
| /linux-6.12.1/drivers/dma/ |
| 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()
612 list_for_each_entry_safe(promise, tmp, &contract->demands, list) in sun4i_dma_free_contract()
665 list_add_tail(&promise->list, &contract->demands); in sun4i_dma_prep_dma_memcpy()
[all …]
|
| /linux-6.12.1/Documentation/power/regulator/ |
| D | overview.rst | 49 current limit to meet operation demands.
|
| /linux-6.12.1/Documentation/i2c/ |
| D | slave-interface.rst | 170 state being busy is troublesome. SMBus demands to always ACK the address phase,
|
| /linux-6.12.1/Documentation/networking/ |
| D | nexthop-group-resilient.rst | 71 traffic, and use those to satisfy the new next-hop distribution demands,
|
| /linux-6.12.1/Documentation/gpu/amdgpu/display/ |
| D | dcn-overview.rst | 58 setup or ignored accordingly with userspace demands. For example, if we
|
| /linux-6.12.1/Documentation/power/ |
| D | opp.rst | 108 as per the demands of SoC usage environment.
|
| /linux-6.12.1/drivers/usb/gadget/ |
| D | Kconfig | 299 a simple CDC subset is used, placing fewer demands on USB.
|
| /linux-6.12.1/drivers/usb/gadget/legacy/ |
| D | Kconfig | 133 is used, placing fewer demands on USB.
|
| /linux-6.12.1/Documentation/cdrom/ |
| 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
|
| /linux-6.12.1/Documentation/driver-api/usb/ |
| D | gadget.rst | 37 I/O processing doesn't imply large demands for memory or CPU
|
| /linux-6.12.1/Documentation/admin-guide/media/ |
| D | vivid.rst | 858 demands a lot of the CPU. For large resolutions this becomes
|
| /linux-6.12.1/Documentation/admin-guide/ |
| D | reporting-issues.rst | 248 demands more than other FLOSS projects. We'd love to make it simpler. But
|
| /linux-6.12.1/tools/memory-model/Documentation/ |
| D | explanation.txt | 968 cache coherence demands.
|