| /linux/include/drm/intel/ |
| H A D | xe_sriov_vfio.h | 24 * @xe: the PF &xe_device obtained by calling xe_sriov_vfio_get_pf()
32 * @xe: the PF &xe_device obtained by calling xe_sriov_vfio_get_pf()
44 * @xe: the PF &xe_device obtained by calling xe_sriov_vfio_get_pf()
55 * @xe: the PF &xe_device obtained by calling xe_sriov_vfio_get_pf()
66 * @xe: the PF &xe_device obtained by calling xe_sriov_vfio_get_pf()
75 * @xe: the PF &xe_device obtained by calling xe_sriov_vfio_get_pf()
84 * @xe: the PF &xe_device obtained by calling xe_sriov_vfio_get_pf()
93 * @xe: the PF &xe_device obtained by calling xe_sriov_vfio_get_pf()
102 * @xe: the PF &xe_device obtained by calling xe_sriov_vfio_get_pf()
113 * @xe: the PF &xe_device obtained by calling xe_sriov_vfio_get_pf()
[all …]
|
| /linux/drivers/scsi/isci/ |
| H A 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/Documentation/arch/riscv/ |
| H A D | vector.rst | 16 for processes running under its domain. Calling these interfaces is not
26 Sets the Vector enablement status of the calling thread, where the control
28 mode. Other threads of the calling process are unaffected.
54 Vector enablement status for the calling thread. The calling thread is
62 Vector enablement setting for the calling thread at the next execve()
78 was enabled for the calling thread.
86 * Every successful call overwrites a previous setting for the calling
91 Gets the same Vector enablement status for the calling thread. Setting for
124 * PR_RISCV_V_VSTATE_CTRL_INHERIT is set for the calling process, and the
140 1: https://github.com/riscv/riscv-v-spec/blob/master/calling-convention.adoc
|
| /linux/tools/testing/selftests/bpf/progs/ |
| H A D | verifier_ld_ind.c | 10 __description("ld_ind: check calling conv, r1")
27 __description("ld_ind: check calling conv, r2")
44 __description("ld_ind: check calling conv, r3")
61 __description("ld_ind: check calling conv, r4")
78 __description("ld_ind: check calling conv, r5")
95 __description("ld_ind: check calling conv, r7")
|
| /linux/Documentation/driver-api/media/ |
| H A D | mc-core.rst | 45 Drivers initialise media device instances by calling
47 registered by calling :c:func:`__media_device_register()` via the macro
48 ``media_device_register()`` and unregistered by calling
50 eventually cleaned up by calling :c:func:`media_device_cleanup()`.
65 Drivers initialize entity pads by calling
68 Drivers register entities with a media device by calling
70 and unregistered by calling
82 Drivers initialize and create device node interfaces by calling
84 and remove them by calling:
124 Drivers create pad to pad links by calling:
[all …]
|
| H A 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/tools/testing/selftests/futex/functional/ |
| H A D | futex_wait.c | 49 ksft_print_dbg_msg("Calling private futex_wait on futex: %p\n", futex); in TEST()
55 ksft_print_dbg_msg("Calling private futex_wake on futex: %p\n", futex); in TEST()
85 ksft_print_dbg_msg("Calling shared (page anon) futex_wait on futex: %p\n", futex); in TEST()
91 ksft_print_dbg_msg("Calling shared (page anon) futex_wake on futex: %p\n", futex); in TEST()
126 ksft_print_dbg_msg("Calling shared (file backed) futex_wait on futex: %p\n", futex); in TEST()
132 ksft_print_dbg_msg("Calling shared (file backed) futex_wake on futex: %p\n", futex); in TEST()
|
| /linux/net/netlabel/ |
| H A 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/drivers/base/ |
| H A D | property.c | 121 * It's recommended to call device_property_count_u8() instead of calling
149 * It's recommended to call device_property_count_u16() instead of calling
177 * It's recommended to call device_property_count_u32() instead of calling
205 * It's recommended to call device_property_count_u64() instead of calling
233 * It's recommended to call device_property_string_array_count() instead of calling
324 * It's recommended to call fwnode_property_count_u8() instead of calling
353 * It's recommended to call fwnode_property_count_u16() instead of calling
382 * It's recommended to call fwnode_property_count_u32() instead of calling
411 * It's recommended to call fwnode_property_count_u64() instead of calling
440 * It's recommended to call fwnode_property_string_array_count() instead of calling
[all …]
|
| /linux/Documentation/arch/powerpc/ |
| H A 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/arch/arm/kernel/ |
| H A D | entry-header.S | 234 ldrd r0, r1, [sp, #S_LR] @ calling lr and pc
239 stmdb lr!, {r0, r1, \rpsr} @ calling lr and rfe context
312 ldr r1, [r2, #\offset + S_PSR] @ get calling cpsr
322 ldmdb r2, {r1 - lr}^ @ get calling r1 - lr
324 ldmdb r2, {r0 - lr}^ @ get calling r0 - lr
342 load_user_sp_lr r2, r3, \offset + S_SP @ calling sp, lr
343 ldr r1, [sp, #\offset + S_PSR] @ get calling cpsr
354 ldmdb sp, {r1 - r12} @ get calling r1 - r12
356 ldmdb sp, {r0 - r12} @ get calling r0 - r12
425 * We must set at least "tsk" and "why" when calling ret_with_reschedule.
|
| /linux/Documentation/arch/arm64/ |
| H A D | sme.rst | 173 Sets the vector length of the calling thread and related flags, where
174 arg == vl | flags. Other threads of the calling process are unaffected.
210 * Either the calling thread's vector length or the deferred vector length
217 * Any previously outstanding deferred vector length change in the calling
224 vector length that will be applied at the next execve() by the calling
230 Calling PR_SME_SET_VL with vl equal to the thread's current vector
231 length, or calling PR_SME_SET_VL with the PR_SME_SET_VL_ONEXEC flag,
235 Calling PR_SME_SET_VL with vl equal to the thread's current vector
236 length, or calling PR_SME_SET_VL with the PR_SME_SET_VL_ONEXEC flag,
242 Gets the vector length of the calling thread.
[all …]
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | vidioc-subdev-enum-mbus-code.rst | 117 subdevice when calling the :ref:`VIDIOC_SUBDEV_S_FMT <VIDIOC_SUBDEV_G_FMT>`
124 the subdevice when calling the :ref:`VIDIOC_SUBDEV_S_FMT <VIDIOC_SUBDEV_G_FMT>`
131 subdevice when calling the :ref:`VIDIOC_SUBDEV_S_FMT <VIDIOC_SUBDEV_G_FMT>`
138 subdevice when calling the :ref:`VIDIOC_SUBDEV_S_FMT <VIDIOC_SUBDEV_G_FMT>`
145 the subdevice when calling the :ref:`VIDIOC_SUBDEV_S_FMT <VIDIOC_SUBDEV_G_FMT>`
|
| /linux/tools/testing/selftests/bpf/verifier/ |
| H A D | dead_code.c | 89 .errstr_unpriv = "loading/calling other bpf or kernel functions are allowed for",
107 .errstr_unpriv = "loading/calling other bpf or kernel functions are allowed for",
125 .errstr_unpriv = "loading/calling other bpf or kernel functions are allowed for",
141 .errstr_unpriv = "loading/calling other bpf or kernel functions are allowed for",
156 .errstr_unpriv = "loading/calling other bpf or kernel functions are allowed for",
|
| H A 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/Documentation/core-api/ |
| H A D | maple_tree.rst | 32 them back by calling xa_to_value(). If the user needs to use a reserved
74 You can walk each entry within a range by calling mt_for_each(). You must
87 Finally, you can remove all entries from a maple tree by calling
125 before calling mtree_load(), then take a reference count on the object you
126 have found before calling mtree_unlock(). This will prevent stores from
201 need to occur before a write occurs then calling mas_expected_entries() will
204 insertions are complete calling mas_destroy() on the maple state will free the
|
| /linux/Documentation/power/regulator/ |
| H A D | regulator.rst | 12 Drivers can register a regulator by calling::
20 Regulators can be unregistered by calling::
29 consumer drivers by calling::
|
| /linux/Documentation/filesystems/iomap/ |
| H A D | operations.rst | 203 The pagecache takes whatever locks it needs before calling the
236 before calling this function.
246 exclusive mode before calling this function.
279 mode before calling this function.
290 mode before calling this function.
303 mode before calling this function.
534 Callers commonly hold ``i_rwsem`` in shared mode before calling this
589 calling this function.
652 Callers commonly hold ``i_rwsem`` in shared mode before calling this
674 Callers commonly hold ``i_rwsem`` in exclusive mode before calling this
[all …]
|
| /linux/include/rdma/ |
| H A D | rdma_cm.h | 166 * Note: calling this function has the effect of canceling in-flight
195 * This associates a source address with the RDMA identifier before calling
221 * into an RDMA address before calling this routine.
230 * side of a connection, before calling rdma_resolve_route. The resolution
269 * this call before calling ib_modify_qp.
272 * states can associate a QP with the rdma_cm_id by calling rdma_create_qp().
288 * Users must have bound the rdma_cm_id to a local address by calling
289 * rdma_bind_addr before calling this routine.
|
| /linux/Documentation/pcmcia/ |
| H A 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/arch/arm/include/asm/ |
| H A 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/lib/ |
| H A 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/Documentation/isdn/ |
| H A 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/Documentation/filesystems/caching/ |
| H A D | backend-api.rst | 84 Once the cache is set up, it can be brought online by calling::
98 The cache backend can withdraw a cache from service by calling this function::
107 to withdraw them, calling::
113 wait for completion by calling::
118 volumes, calling::
126 calling::
230 elsewhere. A pointer to this can be obtained by calling::
238 detached from the cookie and a pointer is obtained by calling::
365 to accept I/O again, the backend should release the block by calling::
|
| /linux/Documentation/userspace-api/media/cec/ |
| H A 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
|