Searched full:async (Results 1 – 25 of 90) sorted by relevance
1234
| /Documentation/devicetree/bindings/display/mediatek/ |
| D | mediatek,ethdr.yaml | 61 - description: video frontend 0 async clock
62 - description: video frontend 1 async clock
63 - description: graphic frontend 0 async clock
64 - description: graphic frontend 1 async clock
65 - description: video backend async clock
89 - description: video frontend 0 async reset
90 - description: video frontend 1 async reset
91 - description: graphic frontend 0 async reset
92 - description: graphic frontend 1 async reset
93 - description: video backend async reset
|
| /Documentation/driver-api/ |
| D | mailbox.rst | 44 send a message through before returning) or non-blocking/async mode (submit
53 bool async;
64 if (dc->async) {
100 dc_async->async = true;
110 dc_sync->async = false;
112 /* ASync mailbox is listed second in 'mboxes' property */
116 /* Send async message to remote */
127 /* Now wait for async chan to be done */
|
| /Documentation/driver-api/media/ |
| D | v4l2-async.rst | 3 V4L2 async kAPI
5 .. kernel-doc:: include/media/v4l2-async.h
|
| D | v4l2-core.rst | 22 v4l2-async
|
| D | v4l2-subdev.rst | 184 .. _media-registering-async-subdevs:
216 bridge drivers can then begin to form a list of async connection descriptors
221 Async connection descriptors describe connections to external sub-devices the
222 drivers for which are not yet probed. Based on an async connection, a media data
224 available. There may be one or more async connections to a given sub-device but
225 this is not known at the time of adding the connections to the notifier. Async
226 connections are bound as matching async sub-devices are found, one by one.
236 a path via async sub-devices and notifiers to a notifier that is not an
243 drivers registering their own async connection, but it also registers a notifier
244 and further registers async connections for lens and flash devices found in
[all …]
|
| D | camera-sensor.rst | 64 :ref:`async sub-device registration <media-registering-async-subdevs>`.
|
| /Documentation/devicetree/bindings/gpio/ |
| D | sprd,gpio-eic.yaml | 19 controller contains 4 sub-modules, i.e. EIC-debounce, EIC-latch, EIC-async and
36 The EIC-async sub-module uses a 32kHz clock to capture the short signals
49 - sprd,sc9860-eic-async
62 - sprd,ums512-eic-async
63 - const: sprd,sc9860-eic-async
|
| /Documentation/power/powercap/ |
| D | powercap.rst | 58 │ │ │ ├──async
75 │ │ │ ├──async
84 │ │ ├──async
111 │ │ │ ├──async
128 │ │ │ ├──async
137 │ │ ├──async
142 │ ├──async
|
| /Documentation/devicetree/bindings/infiniband/ |
| D | hisilicon-hns-roce.txt | 22 - interrupts: should contain 32 completion event irq,1 async event irq
26 - hns-roce-async: 1 async event irq
106 "hns-roce-async",
|
| /Documentation/driver-api/memory-devices/ |
| D | ti-gpmc.rst | 74 3. read async muxed
85 4. read async non-muxed
118 7. write async muxed
131 8. write async non-muxed
|
| /Documentation/virt/kvm/devices/ |
| D | s390_flic.rst | 18 - enable/disable for the guest transparent async page faults
58 Enables async page faults for the guest. So in case of a major page fault
59 the host is allowed to handle this async and continues the guest.
62 Disables async page faults for the guest and waits until already pending
63 async page faults are done. This is necessary to trigger a completion interrupt
|
| /Documentation/virt/kvm/x86/ |
| D | cpuid.rst | 55 KVM_FEATURE_ASYNC_PF 4 async pf can be enabled by
73 KVM_FEATURE_ASYNC_PF_VMEXIT 10 paravirtualized async PF VM EXIT
90 before using the second async
92 async pf acknowledgment msr
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | mediatek,smi-common.yaml | 24 base). Besides that, the smi async clock should be prepared and enabled for
61 apb and smi are mandatory. the async is only for generation 1 smi HW.
62 gals(global async local sync) also is optional, see below.
103 - const: async
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | blkio-controller.rst | 153 or async. First two fields specify the major and minor number of the
160 or async. First two fields specify the major and minor number of the
173 the type of operation - read or write, sync or async. First two fields
189 read or write, sync or async. First two fields specify the major and
196 write, sync or async.
201 write, sync or async.
286 or async. First two fields specify the major and minor number of the
293 or async. First two fields specify the major and minor number of the
|
| /Documentation/ABI/testing/ |
| D | configfs-usb-gadget-uac2 | 13 (async/adaptive)
22 fb_max maximum extra bandwidth in async mode
|
| /Documentation/driver-api/mmc/ |
| D | index.rst | 12 mmc-async-req
|
| D | mmc-async-req.rst | 40 https://wiki.linaro.org/WorkingGroups/Kernel/Specs/StoragePerfMMC-async-req
48 truly non-blocking. If there is an ongoing async request it waits
|
| /Documentation/crypto/ |
| D | index.rst | 20 async-tx-api
|
| /Documentation/devicetree/bindings/net/ieee802154/ |
| D | mcr20a.txt | 6 lower than 9000000 depends sync or async operation mode
|
| D | at86rf230.txt | 7 sync or async operation mode
|
| D | cc2520.txt | 6 sync or async operation mode
|
| /Documentation/admin-guide/mm/ |
| D | userfaultfd.rst | 251 any vma registered with write-protection will work in async mode rather
254 In async mode, there will be no message generated when a write operation
277 The page will not be under track of uffd-wp async mode until the page is
280 that was tracked by async mode userfaultfd-wp is invalid.
282 When userfaultfd-wp async mode is used alone, it can be applied to all
311 Guest async page faults, ``FOLL_NOWAIT`` and all other ``GUP*`` features work
312 just fine in combination with userfaults. Userfaults trigger async
429 implementations should continue to use the current async event
|
| /Documentation/gpu/ |
| D | implementation_guidelines.rst | 9 drm-vm-bind-async
|
| /Documentation/devicetree/bindings/iommu/ |
| D | mediatek,iommu.yaml | 26 gals0-rx gals1-rx (Global Async Local Sync rx)
29 gals0-tx gals1-tx (Global Async Local Sync tx)
64 In some SoCs, there may be a GALS(Global Async Local Sync) module between
|
| /Documentation/driver-api/dmaengine/ |
| D | provider.rst | 88 async TX API, to offload operations such as memory copy, XOR,
92 dmaengine was extended. Nowadays, the async TX API is written as a
97 For more information on the Async TX API, please look the relevant
98 documentation file in Documentation/crypto/async-tx-api.rst.
216 available for async transfers.
540 - Should be called at the end of an async TX transfer, and can be
|
1234