Searched full:passed (Results 1 – 25 of 542) sorted by relevance
12345678910>>...22
| /Documentation/misc-devices/ |
| D | pci-endpoint-test.rst | 32 should be passed as argument.
37 to be tested should be passed as argument.
40 to be tested should be passed as argument.
43 should be passed as argument (0: Legacy, 1:MSI, 2:MSI-X).
47 Perform write tests. The size of the buffer should be passed
50 Perform read tests. The size of the buffer should be passed
53 Perform read tests. The size of the buffer should be passed
|
| /Documentation/devicetree/bindings/regulator/ |
| D | regulator.yaml | 128 hardware performs emergency shutdown. Zero can be passed to disable
135 Zero can be passed to disable error detection and value '1' indicates
141 damaged. Recovery actions should be initiated. Zero can be passed to
147 hardware performs emergency shutdown. Zero can be passed to disable
155 Zero can be passed to disable error detection and value '1' indicates
162 damaged. Recovery actions should be initiated. Zero can be passed to
169 hardware performs emergency shutdown. Zero can be passed to disable
177 Zero can be passed to disable error detection and value '1' indicates
184 it gets damaged. Recovery actions should be initiated. Zero can be passed
199 hardware performs emergency shutdown. Zero can be passed to disable
[all …]
|
| /Documentation/arch/s390/ |
| D | vfio-ap-locking.rst | 72 device driver is using it to plug/unplug AP devices passed through to the KVM
78 AP devices passed through to a KVM guest.
81 if the adapter is passed through to a KVM guest, it will have to be
82 unplugged. In order to figure out whether the adapter is passed through,
85 the mediated device is passed through (matrix_mdev->kvm != NULL) and if so,
89 pointer is not used to plug/unplug devices passed through to the KVM guest;
|
| /Documentation/core-api/ |
| D | printk-formats.rst | 105 known are printed in decimal, while a non-ERR_PTR passed as the
219 Passed by reference.
232 Passed by reference.
244 Passed by reference.
320 Passed by reference.
339 Passed by reference.
358 Passed by reference.
373 specified through ``IS`` or ``iS``, can be passed to this format specifier.
389 Passed by reference.
415 Passed by reference.
[all …]
|
| D | genalloc.rst | 29 So, if min_alloc_order is passed as 3, then all allocations will be a
99 with gen_pool_set_algo(). The data value is passed to the
108 alignment (passed via data in a genpool_data_align structure).
115 - gen_pool_fixed_alloc allocates at a specific offset (passed in a
|
| D | dma-api.rst | 68 size and dma_handle must all be the same as those passed into
136 This puts memory back into the pool. The pool is what was passed to
327 Unmaps the region previously mapped. All the parameters passed in
328 must be identical to those passed in (and returned) by the mapping
380 than <nents> passed in if some elements of the scatter/gather list are
421 must be the same as those and passed in to the scatter/gather mapping
424 Note: <nents> must be the number you passed in, *not* the number of
451 as those passed into the sg mapping API. With the sync_single API,
453 those passed into the single mapping API to do a partial sync.
609 by the passed in device, but which need explicit management of memory ownership
[all …]
|
| /Documentation/arch/loongarch/ |
| D | booting.rst | 10 Information passed from BootLoader to kernel
13 LoongArch supports ACPI and FDT. The information that needs to be passed
17 The kernel is passed the following arguments on `kernel_entry` :
|
| /Documentation/kbuild/ |
| D | kbuild.rst | 89 Additional flags to be passed to $(HOSTCC) when building host programs.
93 Additional flags to be passed to $(HOSTCXX) when building host programs.
97 Additional flags to be passed to $(HOSTRUSTC) when building host programs.
101 Flags to be passed when linking Rust proc macros. Since proc macros are loaded
108 If unset, it defaults to the flags passed when linking host programs.
112 Additional flags to be passed when linking host programs.
249 makefile but the argument can be passed to make if needed.
276 makefile but the argument can be passed to make if needed.
289 This variable allows a passphrase or PIN to be passed to the sign-file
330 be a string that can be passed to date -d. The default value
|
| /Documentation/infiniband/ |
| D | tag_matching.rst | 51 pre-posted receive for this arriving message, it is passed to the software and
63 pre-posted receive to this list, this receive is passed to the hardware.
67 list is used to detect the case that a pre-posted receive is passed to the
68 hardware, as the matching unexpected message is being passed from the hardware
|
| /Documentation/driver-api/ |
| D | isa.rst | 11 finding their hardware due to a probe() error not being passed up
42 The passed in isa_driver struct is the regular driver struct embedding a
46 The "SNDRV_CARDS" you see being passed in is a "unsigned int ndev"
70 values have been passed in) and .probe() for everything else. This is
78 loops over the passed in ndev creating devices and registering them.
|
| /Documentation/filesystems/nfs/ |
| D | rpc-cache.rst | 65 dropped. The pointer passed is to the 'ref' field
113 This will be passed to ->match to identify the target entry. If no
117 The item returned is typically passed to cache_check which will check
123 cache_check can be passed a "struct cache_req\*". This structure is
132 The value returned by sunrpc_cache_lookup_rcu can also be passed to
134 passed which should hold the content. If the item found by _lookup
152 passed as a whole to the cache for parsing and interpretation.
|
| /Documentation/networking/ |
| D | x25-iface.rst | 10 This is a description of the messages to be passed between the X.25 Packet
18 needs to be passed to and from the Packet Layer for proper operation.
32 passed down.
|
| D | tls-offload.rst | 59 request, records are retrieved from the socket and passed to decryption routine.
162 For segments passed in order, the driver marks the packets with
183 (descriptor) passed to the host.
218 segment has to be passed to the device as part of the packet context,
274 Green segments are successfully decrypted, blue ones are passed
280 Segment 3 is passed untouched, because due to lack of data from segment 2
285 of expected window of the device so it's passed as is without special
291 a record header and arrived after the next record header has already passed:
333 Special care has to be taken if the confirmation request is passed
383 had been handled successfully and authenticated or the packet has to be passed
[all …]
|
| /Documentation/driver-api/firmware/ |
| D | fw_search_path.rst | 14 The module parameter ''path'' can be passed to the firmware_class module
16 only be up to 256 characters long. The kernel parameter passed would be:
|
| /Documentation/driver-api/nvdimm/ |
| D | security.rst | 81 passed in.
110 of 0 can be passed in to indicate no key.
116 should be injected and its keyid should be passed in via sysfs.
124 master passphrase key is passed to the kernel. The master passphrase key
135 passphrase key is passed to the kernel. The master passphrase key is just
|
| /Documentation/userspace-api/media/v4l/ |
| D | pixfmt-compressed.rst | 71 required to be passed through the ``V4L2_CID_STATELESS_H264_SPS``,
121 Metadata associated with the frame to decode is required to be passed
165 Metadata associated with the frame to decode is required to be passed
187 Metadata associated with the frame to decode is required to be passed
215 Metadata associated with the frame to decode is required to be passed
237 Metadata associated with the frame to decode is required to be passed
268 frame to decode is required to be passed through the
|
| D | vidioc-qbuf.rst | 74 passed array of struct :c:type:`v4l2_plane` have to be used
88 API is used the ``m.fd`` fields of the passed array of struct
103 in use. Setting it means that the buffer will not be passed to the driver
133 array must be passed in as well.
140 API is used the ``m.fd`` fields of the passed array of struct
|
| /Documentation/filesystems/ |
| D | fiemap.rst | 41 with all flags passed, the contents of fm_flags will be unmodified.
69 number of elements in the fiemap_extents[] array should be passed via
193 ->fiemap is passed struct fiemap_extent_info which describes the
197 unsigned int fi_flags; /* Flags as passed from user */
214 The struct fieinfo should be passed in as received from ioctl_fiemap(). The
215 set of fiemap flags which the fs understands should be passed via fs_flags. If
229 fiemap_fill_next_extent() will use the passed values to populate the
|
| /Documentation/ABI/testing/ |
| D | configfs-stp-policy-p_sys-t | 29 passed since the previous packet from this source. Zero is
37 this many milliseconds have passed since the previous
|
| /Documentation/devicetree/bindings/usb/ |
| D | usb.yaml | 41 selected. In case this isn't passed via DT, USB controllers should
49 isn't passed via DT, USB controllers should default to their maximum HW
|
| /Documentation/filesystems/iomap/ |
| D | operations.rst | 126 the filesystem holds when the mapping is passed back to
186 ``IOMAP_WRITE`` or ``IOMAP_WRITE`` | ``IOMAP_NOWAIT`` will be passed as
196 ``IOMAP_WRITE | IOMAP_FAULT`` will be passed as the ``flags`` argument
229 ``IOMAP_ZERO`` will be passed as the ``flags`` argument to
240 ``IOMAP_WRITE | IOMAP_UNSHARE`` will be passed as the ``flags`` argument
253 ``IOMAP_ZERO`` will be passed as the ``flags`` argument to
263 The ``mapping`` and ``wbc`` parameters should be passed unchanged.
401 The direction of the I/O is determined from the ``iocb`` passed in.
610 For a read fault, ``IOMAP_DAX | IOMAP_FAULT`` will be passed as the
613 passed as the ``flags`` argument to ``->iomap_begin``.
[all …]
|
| /Documentation/bpf/ |
| D | graph_ds_impl.rst | 94 bpf_rbtree_add(&tree, n); /* PASSED */
106 (``ACQUIRED`` and ``PASSED`` comments in the example denote statements where
107 "ownership is acquired" and "ownership is passed", respectively)
109 What should the verifier do with ``n`` after ownership is passed off? If the
115 When ownership is passed to ``tree`` via ``bpf_rbtree_add`` the answer is less
127 bpf_rbtree_add(&tree, n); /* PASSED */
|
| D | kfuncs.rst | 115 annotation, the verifier will reject the program if the dynptr passed in is
122 argument may be null. If the function is passed a nullptr in place of the buffer,
135 annotation, the verifier will reject the program if a null pointer is passed in with
225 passed in to it. There can be only one referenced pointer that can be passed
235 BTF objects have been passed in their unmodified form (that is, at a zero
241 1. Pointers which are passed as tracepoint or struct_ops callback arguments.
244 Pointers to non-BTF objects (e.g. scalar pointers) may also be passed to
369 The verifier will always enforce that the BTF type of a pointer passed to a
372 according to the C standard to be passed to the same kfunc arg, even if their
384 The verifier would allow a ``struct bpf_cpumask *`` to be passed to a kfunc
[all …]
|
| /Documentation/admin-guide/ |
| D | efi-stub.rst | 45 Arguments to the kernel can be passed after bzImage.efi, e.g.::
55 stub-specific command line parameter, everything else is passed to the
80 is passed to bzImage.efi.
|
| /Documentation/block/ |
| D | writeback_cache_control.rst | 73 For bio based drivers the REQ_PREFLUSH and REQ_FUA bit are simply passed on to
77 *NOTE*: The REQ_FUA bit also gets passed on when the BLK_FEAT_FUA flags is
92 When the BLK_FEAT_FUA flags is set, the REQ_FUA bit is simply passed on for the
|
12345678910>>...22