| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-6.6/Documentation/riscv/ |
| 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
|
| /kernel/linux/linux-5.10/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",
|
| /kernel/linux/linux-5.10/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::
|
| /kernel/linux/linux-6.6/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::
|
| /kernel/linux/linux-6.6/Documentation/driver-api/media/ |
| 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 …]
|
| /kernel/linux/linux-6.6/tools/testing/selftests/bpf/progs/ |
| 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")
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/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 the
112 vsyscall calling sequence matches the syscall calling sequence, with the
113 following differences. Some vsyscalls may have different calling sequences.
|
| /kernel/linux/linux-6.6/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()
|
| /kernel/linux/linux-6.6/drivers/base/ |
| D | property.c | 82 * It's recommended to call device_property_count_u8() instead of calling
110 * It's recommended to call device_property_count_u16() instead of calling
138 * It's recommended to call device_property_count_u32() instead of calling
166 * It's recommended to call device_property_count_u64() instead of calling
194 * It's recommended to call device_property_string_array_count() instead of calling
285 * It's recommended to call fwnode_property_count_u8() instead of calling
314 * It's recommended to call fwnode_property_count_u16() instead of calling
343 * It's recommended to call fwnode_property_count_u32() instead of calling
372 * It's recommended to call fwnode_property_count_u64() instead of calling
401 * It's recommended to call fwnode_property_string_array_count() instead of calling
[all …]
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | vidioc-subdev-enum-mbus-code.rst | 95 subdevice when calling the :ref:`VIDIOC_SUBDEV_S_FMT <VIDIOC_SUBDEV_G_FMT>`
102 the subdevice when calling the :ref:`VIDIOC_SUBDEV_S_FMT <VIDIOC_SUBDEV_G_FMT>`
109 subdevice when calling the :ref:`VIDIOC_SUBDEV_S_FMT <VIDIOC_SUBDEV_G_FMT>`
116 subdevice when calling the :ref:`VIDIOC_SUBDEV_S_FMT <VIDIOC_SUBDEV_G_FMT>`
123 the subdevice when calling the :ref:`VIDIOC_SUBDEV_S_FMT <VIDIOC_SUBDEV_G_FMT>`
|
| /kernel/linux/linux-6.6/tools/testing/selftests/bpf/verifier/ |
| 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",
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/v4l/ |
| 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>`
|
| /kernel/linux/linux-6.6/tools/testing/selftests/bpf/ |
| D | DENYLIST.s390x | 16 ksyms_module_libbpf # JIT does not support calling kernel function …
28 xdp_metadata # JIT does not support calling kernel function …
29 test_task_under_cgroup # JIT does not support calling kernel function …
|
| /kernel/linux/linux-6.6/arch/arm/kernel/ |
| 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.
|