| /Linux-v5.15/drivers/scsi/isci/ |
| D | isci.h | 130 * This value indicates that the calling method completed successfully,
178 * This member indicates the calling function failed, because the state
184 * This member indicates the calling function failed, because there is
190 * This member indicates the calling function failed, because the
196 * This member indicates the calling function failed, because the
202 * This member indicates the calling function failed, because the
208 * This member indicates the calling function failed, because the
214 * This member indicates the calling function failed, because the
221 * This member indicates the calling function failed, because the
227 * This member indicates the calling function failed, because the
[all …]
|
| /Linux-v5.15/tools/testing/selftests/bpf/verifier/ |
| D | ld_ind.c | 2 "ld_ind: check calling conv, r1",
14 "ld_ind: check calling conv, r2",
26 "ld_ind: check calling conv, r3",
38 "ld_ind: check calling conv, r4",
50 "ld_ind: check calling conv, r5",
62 "ld_ind: check calling conv, r7",
|
| D | dead_code.c | 90 .errstr_unpriv = "loading/calling other bpf or kernel functions are allowed for",
108 .errstr_unpriv = "loading/calling other bpf or kernel functions are allowed for",
126 .errstr_unpriv = "loading/calling other bpf or kernel functions are allowed for",
142 .errstr_unpriv = "loading/calling other bpf or kernel functions are allowed for",
157 .errstr_unpriv = "loading/calling other bpf or kernel functions are allowed for",
|
| D | ld_abs.c | 2 "ld_abs: check calling conv, r1",
14 "ld_abs: check calling conv, r2",
26 "ld_abs: check calling conv, r3",
38 "ld_abs: check calling conv, r4",
50 "ld_abs: check calling conv, r5",
62 "ld_abs: check calling conv, r7",
|
| /Linux-v5.15/Documentation/power/regulator/ |
| D | consumer.rst | 12 A consumer driver can get access to its supply regulator by calling ::
39 A consumer can enable its power supply by calling::
48 A consumer can determine if a regulator is enabled by calling::
55 A consumer can disable its supply when no longer needed by calling::
80 Consumers can control their supply voltage by calling::
92 The regulators configured voltage output can be found by calling::
111 Consumers can control their supply current limit by calling::
124 A regulators current limit can be found by calling::
146 by calling::
167 calling::
[all …]
|
| D | regulator.rst | 12 Drivers can register a regulator by calling::
20 Regulators can be unregistered by calling::
29 consumer drivers by calling::
|
| /Linux-v5.15/Documentation/driver-api/media/ |
| D | mc-core.rst | 45 Drivers register media device instances by calling
47 and unregistered by calling :c:func:`media_device_unregister()`.
58 Drivers initialize entity pads by calling
61 Drivers register entities with a media device by calling
63 and unregistered by calling
75 Drivers initialize and create device node interfaces by calling
77 and remove them by calling:
117 Drivers create pad to pad links by calling:
125 Drivers create interface to entity links by calling:
166 Drivers initiate a graph traversal by calling
[all …]
|
| D | v4l2-device.rst | 10 You must register the device instance by calling:
28 If you set it up before calling :c:func:`v4l2_device_register` then it will
30 :c:type:`v4l2_dev <v4l2_device>`\ ->name before calling
49 V4L2 devices are unregistered by calling:
128 decrease the refcount manually as well by calling:
|
| /Linux-v5.15/Documentation/core-api/ |
| D | xarray.rst | 37 a value entry by calling xa_is_value(), and convert it back to
38 an integer by calling xa_to_value().
69 use xa_erase() instead of calling xa_store() with a
84 You can copy entries out of the XArray into a plain array by calling
86 by calling xa_for_each(), xa_for_each_start() or xa_for_each_range().
90 Calling xa_store_range() stores the same entry in a range
110 Finally, you can remove all entries from an XArray by calling
124 by using xa_set_mark() and remove the mark from an entry by calling
126 particular mark set by calling xa_marked(). Erasing an entry from the
238 before calling xa_load(), then take a reference count on the
[all …]
|
| D | gfp_mask-from-fs-io.rst | 15 memory reclaim calling back into the FS or IO paths and blocking on
21 the gfp mask when calling an allocator. GFP_NOFS respectively GFP_NOIO can be
60 to fix up. That means that calling ``vmalloc`` with GFP_NOFS/GFP_NOIO is
|
| /Linux-v5.15/net/netlabel/ |
| D | netlabel_addrlist.c | 43 * responsible for calling the rcu_read_[un]lock() functions.
67 * calling the rcu_read_[un]lock() functions.
93 * responsible for calling the rcu_read_[un]lock() functions.
118 * calling the rcu_read_[un]lock() functions.
145 * for calling the necessary locking functions.
182 * for calling the necessary locking functions.
218 * calling the necessary locking functions.
235 * entry on success, NULL on failure. The caller is responsible for calling
258 * calling the necessary locking functions.
275 * entry on success, NULL on failure. The caller is responsible for calling
|
| /Linux-v5.15/tools/testing/selftests/futex/functional/ |
| D | futex_wait.c | 80 info("Calling private futex_wait on futex: %p\n", futex); in main()
86 info("Calling private futex_wake on futex: %p\n", futex); in main()
108 info("Calling shared (page anon) futex_wait on futex: %p\n", futex); in main()
114 info("Calling shared (page anon) futex_wake on futex: %p\n", futex); in main()
147 info("Calling shared (file backed) futex_wait on futex: %p\n", futex); in main()
153 info("Calling shared (file backed) futex_wake on futex: %p\n", futex); in main()
|
| /Linux-v5.15/arch/arm/kernel/ |
| D | entry-header.S | 235 ldrd r0, r1, [sp, #S_LR] @ calling lr and pc
240 stmdb lr!, {r0, r1, \rpsr} @ calling lr and rfe context
299 ldr r1, [r2, #\offset + S_PSR] @ get calling cpsr
309 ldmdb r2, {r1 - lr}^ @ get calling r1 - lr
311 ldmdb r2, {r0 - lr}^ @ get calling r0 - lr
329 load_user_sp_lr r2, r3, \offset + S_SP @ calling sp, lr
330 ldr r1, [sp, #\offset + S_PSR] @ get calling cpsr
341 ldmdb sp, {r1 - r12} @ get calling r1 - r12
343 ldmdb sp, {r0 - r12} @ get calling r0 - r12
412 * We must set at least "tsk" and "why" when calling ret_with_reschedule.
|
| /Linux-v5.15/Documentation/powerpc/ |
| D | syscall64-abi.rst | 15 with some differences to calling sequence.
17 syscall calling sequence\ [1]_ matches the Power Architecture 64-bit ELF ABI
18 specification C function calling sequence, including register preservation
22 different calling sequences (e.g., rt_sigreturn).
49 Register preservation rules match the ELF ABI calling sequence with some
125 vsyscall calling sequence matches the syscall calling sequence, with the
126 following differences. Some vsyscalls may have different calling sequences.
|
| /Linux-v5.15/Documentation/userspace-api/media/v4l/ |
| D | vidioc-subdev-enum-mbus-code.rst | 99 subdevice when calling the :ref:`VIDIOC_SUBDEV_S_FMT <VIDIOC_SUBDEV_G_FMT>`
106 the subdevice when calling the :ref:`VIDIOC_SUBDEV_S_FMT <VIDIOC_SUBDEV_G_FMT>`
113 subdevice when calling the :ref:`VIDIOC_SUBDEV_S_FMT <VIDIOC_SUBDEV_G_FMT>`
120 subdevice when calling the :ref:`VIDIOC_SUBDEV_S_FMT <VIDIOC_SUBDEV_G_FMT>`
127 the subdevice when calling the :ref:`VIDIOC_SUBDEV_S_FMT <VIDIOC_SUBDEV_G_FMT>`
|
| D | vidioc-enum-fmt.rst | 200 when calling the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl with
207 device when calling the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl with
214 when calling the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl with
221 when calling the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl with
228 device when calling the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl with
|
| /Linux-v5.15/fs/xfs/libxfs/ |
| D | xfs_attr.h | 86 * immediately resume from after being called by the calling function. States
88 * so the calling function needs to pass them back to that subroutine to allow
90 * calling function other than just passing through.
175 * it's calling parent. Only the states relevant to itself or any other
176 * subroutines there in. Once a calling function hands off the state machine to
178 * state machine anymore, and it's the responsibility of that calling function
180 * committed to re-calling that subroutine until it returns something other than
182 * than -EAGAIN), the calling function can resume using the state machine.
432 * calling function to roll the transaction, and then call the subroutine to
|
| /Linux-v5.15/Documentation/userspace-api/media/cec/ |
| D | cec-ioc-adap-g-caps.rst | 79 - Userspace has to configure the physical address by calling
88 - Userspace has to configure the logical addresses by calling
96 - Userspace can transmit CEC messages by calling
106 - Userspace can use the passthrough mode by calling
|
| /Linux-v5.15/Documentation/pcmcia/ |
| D | driver-changes.rst | 37 are reserved, after calling pcmcia_request_configuration(), they may
52 - calling request_irq/free_irq directly. Use the IRQ from `*p_dev->irq`.
70 By calling pcmcia_loop_config(), a driver can iterate over all available
76 Instead of calling pcmcia_release_{configuration,io,irq,win}, all that's
77 necessary now is calling pcmcia_disable_device. As there is no valid
|
| /Linux-v5.15/include/rdma/ |
| D | rdma_cm.h | 147 * Note: calling this function has the effect of canceling in-flight
159 * This associates a source address with the RDMA identifier before calling
185 * into an RDMA address before calling this routine.
222 * this call before calling ib_modify_qp.
225 * states can associate a QP with the rdma_cm_id by calling rdma_create_qp().
241 * Users must have bound the rdma_cm_id to a local address by calling
242 * rdma_bind_addr before calling this routine.
|
| /Linux-v5.15/arch/arm/include/asm/ |
| D | mcpm.h | 76 * mcpm_set_entry_vector() prior to calling this.
87 * mcpm_cpu_power_down - power the calling CPU down
89 * The calling CPU is powered down.
135 * mcpm_cpu_suspend - bring the calling CPU in a suspended state
137 * The calling CPU is suspended. This is similar to mcpm_cpu_power_down()
193 * Clean and disable CPU level cache for the calling CPU. Called on with IRQs
199 * for the calling CPU. No call to cpu_cache_disable will happen for this
|
| /Linux-v5.15/lib/ |
| D | textsearch.c | 38 * (1) User configures a search by calling textsearch_prepare() specifying
42 * (3) User starts the search(es) by calling textsearch_find() or
51 * (7) User destroys the configuration by calling textsearch_destroy().
58 * by calling textsearch_prepare() specifying the searching algorithm,
66 * The actual search is performed by either calling
69 * calling textsearch_find(). Both functions return
71 * no match was found. Subsequent occurrences can be found by calling
|
| /Linux-v5.15/Documentation/isdn/ |
| D | interface_capi.rst | 30 CAPI by calling the Kernel CAPI function attach_capi_ctr() with a pointer to a
34 driver. The registration can be revoked by calling the function
39 structure of the device, and signal its readiness by calling capi_ctr_ready().
52 operation CAPI_REGISTER) to an appropriate hardware driver by calling its
78 the following non-private fields, all to be set by the driver before calling
96 to be set by the driver before calling attach_capi_ctr():
175 to be filled in before calling capi_ctr_ready():
216 * second Calling party number (CONNECT_IND)
|
| /Linux-v5.15/include/linux/ |
| D | ccp.h | 160 * Variables required to be set when calling ccp_enqueue_cmd():
225 * Variables required to be set when calling ccp_enqueue_cmd():
278 * Variables required to be set when calling ccp_enqueue_cmd():
335 * Variables required to be set when calling ccp_enqueue_cmd():
369 * Variables required to be set when calling ccp_enqueue_cmd():
429 * Variables required to be set when calling ccp_enqueue_cmd():
458 * Variables required to be set when calling ccp_enqueue_cmd():
571 * Variables required to be set when calling ccp_enqueue_cmd():
632 * Variables required to be set when calling ccp_enqueue_cmd():
|
| /Linux-v5.15/Documentation/PCI/ |
| D | pci.rst | 173 decrement the reference count on these devices by calling pci_dev_put().
200 the PCI device by calling pci_enable_device(). This will:
212 pci_request_resources() before calling pci_enable_device().
249 calling pci_disable_device().
254 determine MMIO and IO Port resource availability _after_ calling
276 to "register" this capability by calling pci_set_dma_mask() with
285 address by calling pci_set_consistent_dma_mask().
309 While calling request_irq() is the last step described here,
332 MSI capability can be enabled by calling pci_alloc_irq_vectors() with the
333 PCI_IRQ_MSI and/or PCI_IRQ_MSIX flags before calling request_irq(). This
[all …]
|
