| /Linux-v5.15/Documentation/power/regulator/ |
| D | regulator.rst | 12 Drivers can register a regulator by calling::
20 Regulators can be unregistered by calling::
29 consumer drivers by calling::
|
| 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 …]
|
| /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/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/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/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/virt/kvm/arm/ |
| D | pvtime.rst | 20 These are only available in the SMC64/HVC64 calling convention as
23 ARCH_FEATURES mechanism before calling it.
47 PV_TIME_ST returns the structure for the calling VCPU.
|
| D | ptp_kvm.rst | 12 This hypercall uses the SMC32/HVC32 calling convention:
|
| /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/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
|
| /Linux-v5.15/Documentation/core-api/ |
| 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 | 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().
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
239 object you have found before calling xa_unlock(). This will
[all …]
|
| D | idr.rst | 28 the pointer you associated with the ID by calling idr_find()
29 and free the ID by calling idr_remove().
|
| /Linux-v5.15/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
|
| /Linux-v5.15/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.
|
| /Linux-v5.15/arch/arm/kernel/ |
| D | entry-header.S | 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
|
| /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():
|
| /Linux-v5.15/Documentation/bpf/ |
| D | bpf_design_QA.rst | 26 BPF is generic instruction set *with* C calling convention.
29 Q: Why C calling convention was chosen?
36 defines calling convention that is compatible with C calling
45 A: NO. BPF calling convention only allows registers R1-R5 to be used
62 Q: Does C-calling convention diminishes possible use cases?
262 Q: Directly calling kernel function is an ABI?
|
| /Linux-v5.15/Documentation/networking/ |
| D | netdevices.rst | 53 /* ... do all device setup before calling register_netdev() ...
74 Note that after calling register_netdev() the device is visible in the system.
140 * will take care of calling my_destructor and free_netdev().
163 so if register_netdevice() fails driver is responsible for calling
226 not by user space calling ioctl as it was in before
|
| /Linux-v5.15/net/x25/ |
| 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-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 …]
|
| /Linux-v5.15/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
|
| /Linux-v5.15/security/tomoyo/ |
| D | Kconfig | 43 bool "Activate without calling userspace policy loader."
69 string "Trigger for calling userspace policy loader"
|
