Searched full:calling (Results 1 – 25 of 391) sorted by relevance
12345678910>>...16
| /Documentation/arch/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
|
| /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::
|
| /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 …]
|
| 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:
|
| /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
|
| 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
|
| D | folio_queue.rst | 62 A segment should be initialised by calling::
74 Folios can be set in the next unused slot in a segment struct by calling one
89 A folio can be excised by calling::
147 used to note information such as if a folio needs folio_put() calling upon it.
|
| /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>`
|
| 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
|
| /Documentation/arch/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.
|
| /Documentation/devicetree/bindings/arm/firmware/ |
| D | sdei.txt | 12 below) and passing arguments in a manner specified by the "SMC Calling
30 - method : The method of calling the SDEI firmware. Permitted
|
| /Documentation/bpf/standardization/ |
| D | abi.rst | 11 Registers and calling convention
17 The BPF calling convention is defined as:
|
| /Documentation/ABI/testing/ |
| D | dell-smbios-wmi | 13 first determine the minimum size of the calling interface
22 2) After you've determined the minimum size of the calling
|
| /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
|
| /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
|
| /Documentation/arch/arm64/ |
| D | sme.rst | 183 Sets the vector length of the calling thread and related flags, where
184 arg == vl | flags. Other threads of the calling process are unaffected.
220 * Either the calling thread's vector length or the deferred vector length
227 * Any previously outstanding deferred vector length change in the calling
234 vector length that will be applied at the next execve() by the calling
240 Calling PR_SME_SET_VL with vl equal to the thread's current vector
241 length, or calling PR_SME_SET_VL with the PR_SME_SET_VL_ONEXEC flag,
245 Calling PR_SME_SET_VL with vl equal to the thread's current vector
246 length, or calling PR_SME_SET_VL with the PR_SME_SET_VL_ONEXEC flag,
252 Gets the vector length of the calling thread.
[all …]
|
| /Documentation/driver-api/ |
| D | pwrseq.rst | 52 specify the name of the target it wants to reach in the sequence after calling
53 pwrseq_power_up(). The descriptor can be released by calling pwrseq_put() and
70 register with the pwrseq subsystem by calling pwrseq_device_register().
|
| /Documentation/filesystems/iomap/ |
| D | operations.rst | 178 The pagecache takes whatever locks it needs before calling the
189 before calling this function.
199 exclusive mode before calling this function.
232 mode before calling this function.
243 mode before calling this function.
256 mode before calling this function.
492 Callers commonly hold ``i_rwsem`` in shared mode before calling this
517 calling this function.
580 Callers commonly hold ``i_rwsem`` in shared mode before calling this
602 Callers commonly hold ``i_rwsem`` in exclusive mode before calling this
[all …]
|
| /Documentation/userspace-api/media/mediactl/ |
| D | media-ioc-request-alloc.rst | 45 In addition, the request can be queued by calling
46 :ref:`MEDIA_REQUEST_IOC_QUEUE` and re-initialized by calling
|
| /Documentation/mhi/ |
| D | topology.rst | 57 * Prepares the device for transfer by calling mhi_prepare_for_transfer.
58 * Initiates data transfer by calling mhi_queue_transfer.
|
| /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)
|
| /Documentation/filesystems/caching/ |
| 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::
|
| /Documentation/filesystems/ |
| D | journalling.rst | 27 calling jbd2_journal_load().
112 layer for calling the callback by simply setting
149 gets permission from JBD2 to do so by calling the function
151 file system should tell JBD2 about it by calling
153 commit immediately after stopping the fast commit it can do so by calling
|
12345678910>>...16