| /linux/Documentation/arch/riscv/ |
| H A D | vector.rst | 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/Documentation/power/regulator/ |
| H A 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 …]
|
| 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/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/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/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>`
|
| H A D | vidioc-streamon.rst | 59 the same state as after calling
67 calling :ref:`VIDIOC_REQBUFS` and can be restarted
|
| /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
|
| /linux/Documentation/bpf/standardization/ |
| H A D | abi.rst | 11 Registers and calling convention
17 The BPF calling convention is defined as:
|
| /linux/Documentation/virt/kvm/arm/ |
| H A D | pvtime.rst | 20 These are only available in the SMC64/HVC64 calling convention as
23 ARCH_FEATURES mechanism before calling it.
49 PV_TIME_ST returns the structure for the calling VCPU.
|
| /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/Documentation/ABI/testing/ |
| H A 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
|
| /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
|
| H A 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().
86 You can copy entries out of the XArray into a plain array by calling
88 by calling xa_for_each(), xa_for_each_start() or xa_for_each_range().
112 Finally, you can remove all entries from an XArray by calling
126 by using xa_set_mark() and remove the mark from an entry by calling
128 particular mark set by calling xa_marked(). Erasing an entry from the
240 before calling xa_load(), then take a reference count on the
241 object you have found before calling xa_unlock(). This will
339 If the xa_state is holding an ``ENOMEM`` error, calling xas_nome
[all...] |
| H A 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.
|
| H A D | idr.rst | 31 the pointer you associated with the ID by calling idr_find()
32 and free the ID by calling idr_remove().
|
| /linux/Documentation/userspace-api/media/mediactl/ |
| H A 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
|
| /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():
|
| /linux/net/x25/ |
| H A D | af_x25.c | 121 char *called, *calling; in x25_addr_ntoa() local
128 calling = calling_addr->x25_addr; in x25_addr_ntoa()
141 *calling++ = ((*p >> 0) & 0x0F) + '0'; in x25_addr_ntoa()
144 *calling++ = ((*p >> 4) & 0x0F) + '0'; in x25_addr_ntoa()
149 *called = *calling = '\0'; in x25_addr_ntoa()
158 char *called, *calling; in x25_addr_aton() local
162 calling = calling_addr->x25_addr; in x25_addr_aton()
165 calling_len = strlen(calling); in x25_addr_aton()
180 *p |= (*calling++ - '0') << 0; in x25_addr_aton()
184 *p |= (*calling++ - '0') << 4; in x25_addr_aton()
|
| /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/mhi/ |
| H A D | topology.rst | 57 * Prepares the device for transfer by calling mhi_prepare_for_transfer.
58 * Initiates data transfer by calling mhi_queue_transfer.
|
| /linux/arch/arm/kernel/ |
| H A D | entry-header.S | 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
|
| /linux/Documentation/PCI/ |
| H A 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 dma_set_mask() with
285 address by calling dma_set_coherent_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 …]
|
| /linux/Documentation/filesystems/ |
| H A 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
|